[antlr-interest] ANTLR V3 parser syntax for ~

[Loring Craymer]

Ter

The problem is in codegen.g; antlr.g builds a usable tree for elements, but
codegen.g only recognizes ast_suffixes for "atom".

That reminds me:  someone a few weeks back posted a note saying that they
had a token sequence generator for verifying compatibility between manually
generated tree grammars and the parse grammar that generates the trees.
Perhaps it would be a good idea to apply that to the antlr 3 tree grammars;
the grammars are still not strong on consistency.

--Loring

> -----Original Message-----
> From: antlr-interest-bounces at antlr.org [mailto:antlr-interest-
> bounces at antlr.org] On Behalf Of Terence Parr
> Sent: Monday, June 26, 2006 4:19 PM
> To: ANTLR Interest
> Subject: Re: [antlr-interest] ANTLR V3 parser syntax for ~
> 
> On Jun 26, 2006, at 2:22 PM, Ari Steinberg wrote:
> 
> > No dice, it's still not one bit happy.  Here's a copy of what I've got
> > so far, maybe you'll see something I'm not.
> 
> Crap...you found some the few things on the todo list.  Bangs on
> wildcard and sets....damn!  Probably easy to fix, but is it ok if I
> go out with beta and fix for 3.0 final?
> 
> For the value rlue, try this for now:
> 
> value:
>          ( ~STATEMENT_END {$value.setType(VALUE);} )+
> ;
> 
> Ter