Re: type clash on default action: <NONE> != <>

> From: Michael Widenius
> Date: Tue, 10 Dec 2002 15:42:26 +0200
>
> 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.

That should work for now, but you have to use NONE systematically: you
have to use it for all the terminals and nonterminals that do not have
an associated value, at least for terminals and nonterminals that
appear as the first item in the left-hand side of a rule.

Once the next version of Bison comes out, you should be able to remove
NONE entirely; it shouldn't be needed.