Re: --yacc and token #define's

[Joel E. Denny]

On Sat, 10 Jun 2006, Paul Eggert wrote:

> "Joel E. Denny" <address@hidden> writes:
> 
> > We didn't discuss removing the enum in the presence of --yacc.  That would 
> > make `bison -y' more yacc-like, I guess.  Any reason not to remove it? 
> 
> It would make the output of "bison -y" harder to debug with GDB, on
> some platforms.

I thought about this, but I was thinking there was some Yacc issue with 
putting extra stuff in the header.  Something Akim said when we were 
discussing the pre-prologues in the header a while back.  Oh well, I can't 
find it now.

> Is there any harm to keeping the enum?

Not for me.  I guess it's been around long enough with no complaints that 
I shouldn't have worried about it.  I'll just leave it.

> > The man page still states that --fixed-output-files is equivalent to 
> > --yacc
> 
> I'd forgotten all about the man page.  Ouch.  The man page should be
> generated automatically from "bison --help".  (But this is another
> matter.)

Ok, so I should just leave "doc/bison.1" untouched for now?  That is, 
you'll implement this eventually?

Joel