[Top][All Lists]

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

Re: [RFA] Java skeleton

From: Paolo Bonzini
Subject: Re: [RFA] Java skeleton
Date: Tue, 27 Feb 2007 10:30:29 +0100
User-agent: Thunderbird (Macintosh/20061207)

Not in the C++ skeleton, which I based the Java naming convention on.

As far as I understand the C++ skeletons, the user cannot add new members to the parser class. I'm not sure why the "yy" prefix is ever used internally at all.

Thanks for the clarification.

Your Java skeletons do allow users to add members to the parser and lexer classes, so it seems to me that you have much more to worry about. I find it hard to believe that you will never decide to add some new really useful public method.

I find it hard that this wouldn't have been added already in the C skeleton. :-)

Still, from the point of view of the parser's end user (who may not even know what Bison is), it seems ugly to have a public interface where some large arbitrary portion of the methods have names prefixed by yy.

Yes, that's the reason why I think parse() should remain unprefixed, for example.


reply via email to

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