Re: type clash on default action: <NONE> != <>
am 10.12.2002 14:42:26 von Michael WideniusHi!
>>>>> "Paul" == Paul Eggert
>> From: Sinisa Milivojevic
>> Date: Mon, 2 Dec 2002 14:37:12 +0200
>> Actually we use 1.35 only and have not changed our code to support
>> 1.75 or similar.
Paul> If I were you I wouldn't bother with 1.75; I'd wait for the next
Paul> official release of Bison.
Paul> Is there an easy way that I can browse the development history of
Paul> sql/sql_yacc.yy to see where the
Paul> why? It might help us Bison folks improve backward compatibility if
Paul> we know why the grammar is the way it is.
If I remember correctly we started to use NONE very early in MySQL
development to go around some warnings that we got from bison and the
none part has been growing ever sense.
Now we routinely add new stuff to the NONE part when we get an error
about a type clash from bison.
Regards,
Monty
--
For technical support contracts, goto https://order.mysql.com/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Michael Widenius
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, CTO
/_/ /_/\_, /___/\___\_\___/ Helsinki, Finland
<___/ www.mysql.com
------------------------------------------------------------ ---------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail bugs-thread13251@lists.mysql.com
To unsubscribe, e-mail