[antlr-interest] Missing characters in partial matches
Matt Palmer
mattpalms at gmail.com
Sat Aug 23 08:50:52 PDT 2008
Just a quick thank you to everyone who's responded. I feel like I have a
better grasp on what's going on now. I'm going to have a play, and look at
the tokens DFA (or even the code, if that doesn't enlighten me). I'm keen
to understand how the v3 lexer actually works, but also how it might
otherwise work too :)
cheers,
MattP.
On Sat, Aug 23, 2008 at 1:05 PM, Thomas Brandon <tbrandonau at gmail.com>wrote:
> On Sat, Aug 23, 2008 at 9:04 PM, Gavin Lambert <antlr at mirality.co.nz>
> wrote:
> > At 17:14 23/08/2008, Thomas Brandon wrote:
> > (When I say "the lexer can act like it's LL(1)", I don't really mean that
> > it's LL(1) all the time, just that you need to be aware that it tries to
> use
> > the minimum amount of lookahead that it thinks it can get away with,
> which
> > is often only a single character -- and not always sufficient to
> completely
> > disambiguate, especially when loops and optional paths are involved.)
> >
> >
> My point was that the known issue only affects choosing between
> multiple token sequences. Any other cases where it insufficiently
> disambiguates between multiple single token alternates, no matter how
> many loops or optional paths you have, are an additional issue and
> should be reported as such. I'm not aware of any other cases where
> lookahead is insufficient.
>
> Tom.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.antlr.org/pipermail/antlr-interest/attachments/20080823/557c793b/attachment.html
More information about the antlr-interest
mailing list