Hi Jan,
I’ve (finally!) pushed the LALR update from upstream to the ‘stable-2.0’
branch.
Thanks again, and sorry for the delay.
Ludo’.
Ludovic Courtès writes:
Hi,
>>> I don’t think this is needed. Lexers are expected to use
>>> ‘make-lexical-token’ and ‘make-source-location’ from (system base lalr)
>>> to preserve source location information.
>> I hope you're right...and that's what I tried, but I didn't get it
>> working. Po
Hi,
Jan Nieuwenhuizen skribis:
> Ludovic Courtès writes:
>
>> I don’t think this is needed. Lexers are expected to use
>> ‘make-lexical-token’ and ‘make-source-location’ from (system base lalr)
>> to preserve source location information.
>
> I hope you're right...and that's what I tried, but I
Ludovic Courtès writes:
Hi Ludo,
> I don’t think this is needed. Lexers are expected to use
> ‘make-lexical-token’ and ‘make-source-location’ from (system base lalr)
> to preserve source location information.
I hope you're right...and that's what I tried, but I didn't get it
working. Possibly
Hi, Jan,
Jan Nieuwenhuizen skribis:
> I am using these patches to provide Bison-like source locations that we
> need for error messages and the like. The output of the parser is a
> plain scheme tree, now transparently annotated with source locations
> that match the parsed input file.
I don’t
