[antlr-interest] Abstract tree parser

[Kirby Bohling]

I wish that superClass option was smart about handling debug vs.
non-debug, that's the one thing that annoys me any time I choose that
option is that I can't integrate with most of the cool debuggers
without extra work.  In the land of C++ where I can use templates,
it's easy to resolve that, in Java it's a lot more boiler plate.

Kirby


On Tue, Feb 23, 2010 at 5:37 PM, Jim Idle <jimi at temporal-wave.com> wrote:
> And you should pretty much always use the superClass option for any serious project.
>
> Jim
>
>> -----Original Message-----
>> From: antlr-interest-bounces at antlr.org [mailto:antlr-interest-
>> bounces at antlr.org] On Behalf Of Terence Parr
>> Sent: Tuesday, February 23, 2010 12:09 PM
>> To: Christian Pontesegger
>> Cc: antlr-interest at antlr.org
>> Subject: Re: [antlr-interest] Abstract tree parser
>>
>> Hi. when I need to do this I use superClass option.
>> Ter
>> On Feb 23, 2010, at 11:45 AM, Christian Pontesegger wrote:
>>
>> > Hi,
>> >
>> > I am creating a treeparser in java which needs some methods. I do not
>> > want to put them into the @members section as the code is quite
>> large.
>> > Is there a way to create an abstract class for the parser? Then I
>> could
>> > put the the abstract methods into the @members section and implement
>> > them in a subclass.
>> >
>> > Is there a way to do that?
>> >
>> > thanks
>> > Christian
>> >
>> > List: http://www.antlr.org/mailman/listinfo/antlr-interest
>> > Unsubscribe: http://www.antlr.org/mailman/options/antlr-
>> interest/your-email-address
>>
>>
>> List: http://www.antlr.org/mailman/listinfo/antlr-interest
>> Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-
>> email-address
>
>
>
>
> List: http://www.antlr.org/mailman/listinfo/antlr-interest
> Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address
>