This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: module level flags
- From: dewar at gnat dot com (Robert Dewar)
- To: bkorb at pacbell dot net, zack at codesourcery dot com
- Cc: dewar at gnat dot com, gcc at gcc dot gnu dot org
- Date: Sun, 29 Sep 2002 16:46:48 -0400 (EDT)
- Subject: Re: module level flags
I completely agree with Zack when he says
> This is my last word on the subject - I don't have time for the
> argument. However, your repeated assertion that "the intended use" of
> YYSTYPE is in a manner incompatible with the C standard is
> indefensible. You've *chosen* to define YYSTYPE as "int" in a parser
> that actually wants to store one of several different pointer types in
> that data type. You should never have expected this to work. The
> Bison manual could perhaps be worded more strongly, but it is clear
> enough that one must use %union and %type in a parser of this form.
> (These directives are supported by all modern versions of Yacc, so
> portability is not an excuse here.)
my comment that there was an error in the YACC approach was entirely
incorrect, sorry about that confusion!