7 messages in com.mysql.lists.bugsRe: type clash on default action: <NO...
FromSent OnAttachments
Martin MOKREJŠ02 Dec 2002 02:36 
Sinisa Milivojevic02 Dec 2002 04:36 
Paul Eggert08 Dec 2002 00:17 
Sinisa Milivojevic09 Dec 2002 03:30 
Lenz Grimmer09 Dec 2002 04:22 
Michael Widenius10 Dec 2002 05:42 
Paul Eggert10 Dec 2002 10:51 
Subject:Re: type clash on default action: <NONE> != <>
From:Paul Eggert (egg@twinsun.com)
Date:12/10/2002 10:51:37 AM
List:com.mysql.lists.bugs

From: Michael Widenius <mon@mysql.com> 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.