> Le 20 nov. 2018 à 21:32, Paul Eggert a écrit :
>
> On 11/20/18 12:01 PM, Akim Demaille wrote:
>> -if (false)
>> +if ((false))
>
> This goes too far. If clang is warning about this sort of thing, then we
> should disable that clang warning. Again, compilers should be our servants,
>
> On 20 Nov 2018, at 20:32, Paul Eggert wrote:
>
> On 11/20/18 12:01 PM, Akim Demaille wrote:
>> -if (false)
>> +if ((false))
>
> This goes too far. If clang is warning about this sort of thing, then we
> should disable that clang warning. Again, compilers should be our servants,
>
On 11/20/18 12:01 PM, Akim Demaille wrote:
-if (false)
+if ((false))
This goes too far. If clang is warning about this sort of thing, then we
should disable that clang warning. Again, compilers should be our
servants, not our masters.
___
> Le 20 nov. 2018 à 21:01, Akim Demaille a écrit :
>
> Hi Uxio,
>
> Thanks for the report. I’m installing this (in master).
Actually, I didn’t. I don’t understand the behavior of clang.
On small examples, ((0)) works perfectly, but in the case of
bison’s own parser, I keep getting errors:
Hi Uxio,
Thanks for the report. I’m installing this (in master).
commit 09303ceb3efad33e218acc7d0aa6f9435838192c
Author: Akim Demaille
Date: Tue Nov 20 20:54:02 2018 +0100
warning: avoid warnings about unreachable code
Reported by Uxio Prego.
https://lists.gnu.org/archive/ht
Hi!
> Le 19 nov. 2018 à 16:09, r0ller a écrit :
>
> Hi Akim,
>
> I managed to take the first step and get it running but it wasn’t as easy as
> I thought.
Sorry about that :(
> First, I wanted to take the approach that the 'Simple C++ Example'
> demonstrates in the bison manual. However, I
