Re: Enhancement request: enabling Variant in C parsers

[Hans Åberg]

> On 23 Aug 2018, at 14:18, Akim Demaille <address@hidden> wrote:
> 
> 
>> Le 23 août 2018 à 14:13, Hans Åberg <address@hidden> a écrit :
>> 
>> 
>>> On 23 Aug 2018, at 13:17, Akim Demaille <address@hidden> wrote:
>>> 
>>>> Le 23 août 2018 à 10:18, Hans Åberg <address@hidden> a écrit :
>>>> 
>>>>> 
>>>>> On 23 Aug 2018, at 07:34, Akim Demaille <address@hidden> wrote:
>>>>>> The input file is broken.
>>>>> 
>>>>> You’ll have to be more specific, WFM.
>>>> 
>>>> It generates an error. You might have more than one, say error<k>.txt, and 
>>>> input<k>.txt.
>>> 
>>> That’s not specific.  You say the input file is broken:
>>> which one, and please show what you have.  Or copy-paste from
>>> the terminal what goes wrong.
>> 
>> The file named « input" in the calc++ example directory. :-)
> 
> Ahhh!  There is no such file in the tarball, and therefore it is
> not installed either.
> 
> It’s created by the test when it is run, so you are actually
> referring to ‘make check'.  See the corresponding test
> (examples/calc++/calc++.test) to see what `input` is expected
> to be.
> 
> The input file is not part of the examples as presented to the
> users, it’s part of Bison test suite.  And it’s only an artifact.
> It should be removed when `make check` is done (I’ll fix that).

It might be good with a self-contained calc++ directory, with some input files, 
so that one can copy it, and start experimenting. An idea might be to add 
comments to the lexer, so that they can be added to the input files. Nothing 
advanced, just a little more than what is now.