[antlr-interest] lexer rule precedence

[Ryan Brown]

True is first.  I also tried adding True and Identifier to the tokens list,
(with True first), but that doesn't make any difference. I also added an
ERR: . token like you suggested and that doesn't help.

-- Ryan Brown


On Fri, Mar 18, 2011 at 8:18 PM, Jim Idle <jimi at temporal-wave.com> wrote:

> List it before IDENTIFIER as you have written it here and add a ERR : . ;
> as the last rule to catch non-matches and issue an error.
>
> Jim
>
> > -----Original Message-----
> > From: antlr-interest-bounces at antlr.org [mailto:antlr-interest-
> > bounces at antlr.org] On Behalf Of Ryan Brown
> > Sent: Friday, March 18, 2011 8:15 PM
> > To: antlr-interest at antlr.org
> > Subject: [antlr-interest] lexer rule precedence
> >
> > I have a lexer with rules like this:
> >
> > TRUE : 'true';
> > IDENTIFIER : 'a'..'z'+;
> >
> > The text "true" parses as IDENTIFIER.  How do I get it to parse as
> > TRUE? Do I need to add not and all my keywords to the IDENTIFIER rule?
> > I don't see anything like that in the java grammar.
> >
> > -- Ryan Brown
> >
> > 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
>