[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 00/13] Better error messages
|
From: |
Akim Demaille |
|
Subject: |
Re: [PATCH 00/13] Better error messages |
|
Date: |
Mon, 20 Jan 2020 06:47:13 +0100 |
> Le 18 janv. 2020 à 16:39, Akim Demaille <address@hidden> a écrit :
>
> This series of patches builds on top of the previous one
> (https://lists.gnu.org/r/bison-patches/2020-01/msg00044.html). It
> brings the following features with parse.error=custom or detailed
> (which I prefer to my previous proposal, 'rich').
Pushed to master.
- [PATCH 05/13] regen, (continued)
- [PATCH 05/13] regen, Akim Demaille, 2020/01/18
- [PATCH 06/13] bison: use detailed error messages, Akim Demaille, 2020/01/18
- [PATCH 07/13] regen, Akim Demaille, 2020/01/18
- [PATCH 09/13] tests: check that detailed error messages preserve UTF-8 characters, Akim Demaille, 2020/01/18
- [PATCH 08/13] yacc.c: escape trigraphs in detailed parse.error, Akim Demaille, 2020/01/18
- [PATCH 10/13] parsers: support translatable token aliases, Akim Demaille, 2020/01/18
- [PATCH 12/13] tests: check token internationalization, Akim Demaille, 2020/01/18
- [PATCH 13/13] parsers: issue tname with i18n markup, Akim Demaille, 2020/01/18
- [PATCH 11/13] regen, Akim Demaille, 2020/01/18
- Re: [PATCH 00/13] Better error messages,
Akim Demaille <=