Hi Akim,
I agree, the logging could look better:) You're also right about that I could
introduce some placeholder symbols for my own framework and then I could
generate the parent symbol in user defined action implementations as well. I
also considered that option. The only thing is that first
> On 10 May 2019, at 07:24, Akim Demaille wrote:
>
>> In practice you just need the symbol name as is. Nobody needs the
>> translation,
>
> I beg to disagree. Nobody should translate the keyword "break",
> but
>
>> # bison /tmp/foo.y
>> /tmp/foo.y:1.7: erreur: erreur de syntaxe, : inattendu
On Freitag, 10. Mai 2019 07:24:51 CEST Akim Demaille wrote:
> Hi Christian,
Hi Akim!
> Aren't you referring to LA correction, as implemented in Bison?
>
> https://www.gnu.org/software/bison/manual/html_node/LAC.html
Well no, it is has somewhat in common, but the use cases are differently, see
> On 10 May 2019, at 07:24, Akim Demaille wrote:
>
> 1. there is a real and valid need for the feature, which I still need
> to be convinced of, especially because symbol names are technical
> details!
One can also write better error messages by using these internal yytname_ table
names:
On May 10, 2019, at 5:21 AM, Hans Åberg wrote:
>
>
>> On 10 May 2019, at 07:24, Akim Demaille wrote:
>>
>>> In practice you just need the symbol name as is. Nobody needs the
>>> translation,
>>
>> I beg to disagree. Nobody should translate the keyword "break",
>> but
>>
>>> # bison /tmp/fo
On May 10, 2019, at 6:47 AM, Hans Åberg wrote:
>
>
>> On 10 May 2019, at 07:24, Akim Demaille wrote:
>>
>> 1. there is a real and valid need for the feature, which I still need
>> to be convinced of, especially because symbol names are technical
>> details!
>
> One can also write better err
On Freitag, 10. Mai 2019 06:57:00 CEST Derek Clegg wrote:
> In fact, I do not think error messages in the generated parser should be
> provided by bison, except as a trivial default. Instead, I’d like to see
> bison call a function (which I provide) when a syntax error occurs, with a
> list of what
Hey Christian,
Thanks a lot for taking the time to give details about your use case.
> Le 10 mai 2019 à 15:11, Christian Schoenebeck a
> écrit :
>
> On Freitag, 10. Mai 2019 07:24:51 CEST Akim Demaille wrote:
>
>> Aren't you referring to LA correction, as implemented in Bison?
>>
>> https://
> Le 10 mai 2019 à 16:28, Christian Schoenebeck a
> écrit :
>
> On Freitag, 10. Mai 2019 06:57:00 CEST Derek Clegg wrote:
>> In fact, I do not think error messages in the generated parser should be
>> provided by bison, except as a trivial default. Instead, I’d like to see
>> bison call a func
> On May 10, 2019, at 10:43 AM, Akim Demaille wrote:
>
>
>
>> Le 10 mai 2019 à 16:28, Christian Schoenebeck a
>> écrit :
>>
>> On Freitag, 10. Mai 2019 06:57:00 CEST Derek Clegg wrote:
>>> In fact, I do not think error messages in the generated parser should be
>>> provided by bison, excep
On Freitag, 10. Mai 2019 19:34:54 CEST Akim Demaille wrote:
> And there was nothing that could be shared? A lot of what you described
> below looks like what LAC does. But I am definitely not a LAC expert, nor
> one of your application, obviously :)
Well, you can look at this example:
http://svn
11 matches
Mail list logo
