Hi Ter,
yep, I confirmed that this happens with a fresh build and all
intermediate files cleaned.
Another thing I noticed in this context, which is an independent
feature request: when ANTLR exits with an error, it should also delete
it's output files (or not touch them at all, what ever is easier to
implement). Because now, if I have a make dependency of fooParser.py
on foo.g and ANTLR fails, make will succeed on the next run, because
fooParser.py exists and is newer than foo.g (and in this specific case
contains valid code, because the error was wrong...). That caused
quite some confusion on my side...
-Ben
On Wed, May 7, 2008 at 7:47 PM, Terence Parr <[EMAIL PROTECTED]> wrote:
> crap...looks like i still get an error...i'll try it out.
> Ter
>
> On May 6, 2008, at 1:21 PM, Benjamin Niemann wrote:
>
>
> >
> >
> >
> > Hi,
> >
> > after syncing my client, rules like
> >
> > r41
> > : (INT -> INT) ( ('+' i=INT) -> ^($i $r41) )* ';'
> > ;
> >
> > now produce
> >
> > error(132):
> /home/users/pink/projects/antlr3/runtime/Python/tests/t042ast.g:211:42:
> > reference $r41 is ambiguous; rule r41 is enclosing rule and referenced
> > in the production (assuming enclosing rule)
> >
> > -Ben
> > _______________________________________________
> > antlr-dev mailing list
> > [email protected]
> > http://www.antlr.org:8080/mailman/listinfo/antlr-dev
> >
>
>
_______________________________________________
antlr-dev mailing list
[email protected]
http://www.antlr.org:8080/mailman/listinfo/antlr-dev
