> Ideas for changing the generated Java parsers. I can implement most of
> these. Comments on the interface and semantics would be appreciated.
This is great material, thanks.
> 1. The parser class can be declared public and/or abstract by using the
> ``%define public'' and ``%define abstract''
> I'm only talking interface, not implementation. I don't want a class
> that includes all union members as fields. Rather, the m4 code would
> lookup the ``field'' name in %union and generate the cast like the
> existing code.
Oh, I see. Actually the first implementation was done that way, st
Di-an JAN wrote:
>> From: Paolo Bonzini <[EMAIL PROTECTED]>
>> Date: Tue, 28 Oct 2008 18:59:16 +0100
>> To: [EMAIL PROTECTED], help-bison@gnu.org
>> Subject: Proposals for various changes to the Java parser
>>
>>> 5. Work around Java's ``code
