bison-patches
[Top][All Lists]
Advanced

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

Re: [RFA] Java skeleton


From: Joel E. Denny
Subject: Re: [RFA] Java skeleton
Date: Mon, 26 Feb 2007 21:25:47 -0500 (EST)

Sorry if you've already received this, but we're having email problems 
here.

On Mon, 26 Feb 2007, Joel E. Denny wrote:

> On Mon, 26 Feb 2007, Paolo Bonzini wrote:
> 
> > > I find it hard to understand when you choose to use the yy prefix and when
> > > you don't.  For example, what's the difference between yyerror and error
> > > when the lexer interface resides in the parser class?
> > 
> > I used it for (almost) all the private members, so that they don't clash 
> > with
> > user private members.  There are a couple of missing ones for which I 
> > attach a
> > patch.  Public members are not prefixed.
> 
> So, does this mean you're reserving the right to add/change private 
> members but not public members?  Couldn't public members clash as well?
> 
> These public members are still prefixed: YYACCEPT, YYABORT, YYERROR, 
> YYFAIL, yyrecovering.
> 
> > > Instead of "union_name", how about "value_superclass" or something else
> > > that's Java-oriented?
> > 
> > What about just "stype"?
> 
> Ok.
> 
> > 1) If a "%code lexer" is given, Bison uses it to define a class 
> > YYParser.Lexer
> > class, which is public and non-abstract.  If it is not given, Bison defines 
> > an
> > interface YYParser.Lexer.
> 
> What if the user wants YYParser.Lexer to be an interface and wants to add 
> new methods accessible in the parser actions?
> 




reply via email to

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