bug-bison
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: assert failure at line 1896


From: Frans Englich
Subject: Re: assert failure at line 1896
Date: Mon, 29 May 2006 18:01:26 +0000
User-agent: KMail/1.8.50

On Monday 29 May 2006 17:46, Joel E. Denny wrote:
> On Mon, 29 May 2006, Joel E. Denny wrote:
> > On Mon, 29 May 2006, Akim Demaille wrote:
> > > >>> "Joel" == Joel E Denny <address@hidden> writes:
> > >  >
> > >  > Akim, I believe the const in b4_yysymprint_generate was your
> > >  > commit.  Do you want to require users to typedef YYSTYPE, or should
> > >  > we remove the const?
> > >
> > > Yes, eventually I would like to move away from using macros.
> >
> > Perhaps we should formally deprecate such usage as of 2.3?  Searching for
> > `#define' in the Open Group's yacc spec, I see no discussion of the yacc
> > user ever specifying a #define.  So, macros should be only a Bison
> > backward-compatibility issue, right?

This reminds me of the "Possible to change name of enum yytokentype?" thread 
on help-bison -- it seems related. Perhaps the switch to only using the enum 
will be done in the same go?


Cheers,

                Frans




reply via email to

[Prev in Thread] Current Thread [Next in Thread]