> On 1 Oct 2021, at 23:30, Christian Schoenebeck
> wrote:
>
>> For the purpose of writing out the line in the error messages, this method
>> (using C++) did not work out well, because I have two parsers, one for the
>> language and one for directives, and it turns out to be difficult to pass
On Freitag, 1. Oktober 2021 09:37:52 CEST Hans Åberg wrote:
> > On 28 Sep 2021, at 14:10, Christian Schoenebeck
> > wrote:>
> > On Montag, 27. September 2021 22:07:33 CEST Hans Åberg wrote:
> In order to generate better syntax error messages writing out the input
> line with the error a
> On 28 Sep 2021, at 14:10, Christian Schoenebeck
> wrote:
>
> On Montag, 27. September 2021 22:07:33 CEST Hans Åberg wrote:
In order to generate better syntax error messages writing out the input
line with the error and a line with a marker underneath, I thought of
checking how
> On 27 Sep 2021, at 22:02, Akim Demaille wrote:
>
> Hi Hans,
>
>> Le 27 sept. 2021 à 20:54, Hans Åberg a écrit :
>>
>> In order to generate better syntax error messages writing out the input line
>> with the error and a line with a marker underneath, I thought of checking
>> how Bison doe
On Montag, 27. September 2021 22:07:33 CEST Hans Åberg wrote:
> >> In order to generate better syntax error messages writing out the input
> >> line with the error and a line with a marker underneath, I thought of
> >> checking how Bison does it, but I could not find the place in its
> >> sources.
> On 27 Sep 2021, at 22:02, Akim Demaille wrote:
>
> Hi Hans,
>
>> Le 27 sept. 2021 à 20:54, Hans Åberg a écrit :
>>
>> In order to generate better syntax error messages writing out the input line
>> with the error and a line with a marker underneath, I thought of checking
>> how Bison doe
Hi Hans,
> Le 27 sept. 2021 à 20:54, Hans Åberg a écrit :
>
> In order to generate better syntax error messages writing out the input line
> with the error and a line with a marker underneath, I thought of checking how
> Bison does it, but I could not find the place in its sources. —Specifical
