> > I am reminded of the layout rule, where certain parse
> errors are caught
> > and trigger a re-lexing of the input. Would it be possible to do
> > something similar here, where certain parse errors in a
> line beginning
> > with the special id "foreign" are caught and trigger re-parsing as
[EMAIL PROTECTED] wrote,
> Me:
> > > However, it is definitely wrong for 'foreign' to be treated as a
> > > keyword. Instead, it is a special identifier
>
> Simon:
> > Tricky, at least in LALR(1).
>
> Yes, you are right of course. Backtracking parser combinators had me
> blinded to the sad re
Me:
> > However, it is definitely wrong for 'foreign' to be treated as a
> > keyword. Instead, it is a special identifier
Simon:
> Tricky, at least in LALR(1).
Yes, you are right of course. Backtracking parser combinators had me
blinded to the sad realities of the world. :-)
> There are stan
Malcolm writes:
> Ian noted the following bug:
>
> > * `foreign' seems to have become a keyword ! My program
> uses it as a
> > variable/function name and I had to rename it to avoid a
> parse error.
> > I couldn't find anything about it in my documentation.
>
> As Michael noted, this is a c
