[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bison 3.3.1 released [stable]

From: Hans Åberg
Subject: Re: Bison 3.3.1 released [stable]
Date: Sun, 27 Jan 2019 22:14:29 +0100

> On 27 Jan 2019, at 19:32, Akim Demaille <address@hidden> wrote:
>> Le 27 janv. 2019 à 18:26, Hans Åberg <address@hidden> a écrit :
>>> On 27 Jan 2019, at 16:43, Akim Demaille <address@hidden> wrote:
>>> In Bison 3.3, the new option --update replaces deprecated features with
>>> their modern spelling, but also applies fixes such as eliminating duplicate
>>> directives, etc.
>> This is nice feature. You might add info about along with the warnings when 
>> it discovers something it can fix.
> I think what you mean is done, and documented in the NEWS too.
> *** Generation of fix-its for IDEs/Editors
>   When given the new option -ffixit (aka -fdiagnostics-parseable-fixits),
>   bison now generates machine readable editing instructions to fix some
>   issues.  Currently, this is mostly limited to updating deprecated
>   directives and removing duplicates.

I get that without the option.

>   See the "fix-it:" lines below:
>     foo.y: warning: fix-its can be applied.  Rerun with option '--update'. 
> [-Wother]

It was not prominent enough for me to notice. :-)

Run 'bison --update <file>' to update deprecated features; see the Bison manual 
for further information.

I put the essential information first. Just an input. :-)

>   This uses the same output format as GCC and Clang.

I tried it, and it caught one instance. I haven't tried it with GCC and Clang, 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]