[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: bison for nlp
From: |
Hans Åberg |
Subject: |
Re: bison for nlp |
Date: |
Thu, 8 Nov 2018 14:27:54 +0100 |
> On 7 Nov 2018, at 10:09, r0ller <address@hidden> wrote:
>
> Numbering tokens was introduced in the very beginning and has been questioned
> by myself quite a many times if it's still needed. I didn't give a hard try
> to get rid of it mainly due to one reason: I want to have an error handling
> that tells in case of an error which symbols could be accepted instead of the
> erroneous one just as bison itself does it but in a structured way (as bison
> returns that info in an error message string). Though, I could not come up
> with any better idea when it comes to remapping a token to a symbol.
If the token numbers are replaced by strings "…", the Bison parser will print
those, and they can also be used in the grammar. Would that suffice?
- bison for nlp, r0ller, 2018/11/06
- Re: bison for nlp, Akim Demaille, 2018/11/07
- Re: bison for nlp, r0ller, 2018/11/07
- Re: bison for nlp,
Hans Åberg <=
- Re: bison for nlp, r0ller, 2018/11/08
- Re: bison for nlp, Hans Åberg, 2018/11/08
- Re: bison for nlp, r0ller, 2018/11/08
- Re: bison for nlp, Akim Demaille, 2018/11/08
- Re: bison for nlp, Hans Åberg, 2018/11/09
- Re: bison for nlp, Akim Demaille, 2018/11/09
- Re: bison for nlp, Hans Åberg, 2018/11/09
- improving error message (was: bison for nlp), Akim Demaille, 2018/11/10
- Re: improving error message (was: bison for nlp), Hans Åberg, 2018/11/10
- Re: improving error message (was: bison for nlp), Akim Demaille, 2018/11/10