Re: new pacification suggestion?
Uxio Prego <[email protected]>
| Newsgroups | gmane.comp.parsers.bison.general |
|---|---|
| Message-ID | <[email protected]> |
So the problem was in an upper scope, a label never jumped to. Please forgive me this little off-topic: I'm having the same alert in https://github.com/westes/flex/blob/98018e3f58d79e082216d406866942841d4bdf8a/src/flex.skl#L1394 didn't report there yet. For no particular reason other I maybe wanted to report one by one and I was already registered in this list. There, unlike in the Bison case, I can't see any comment noting that I might be misusing some known utility supposed to be used. So if the Bison case is relevant, I guess this one is more relevant. > On 25 Nov 2018, at 10:28, Akim Demaille <[email protected]> wrote: > > > >> Le 20 nov. 2018 à 23:18, Akim Demaille <[email protected]> a écrit : >> >> I don’t have any problems with having two pairs of parens, after all we’ve done that forever in the case of assignments in if’s etc. That’s a clear way to tell the others, including the compiler, that something fishy is intentional (until ‘sic’ becomes a keyword). >> >> The problem here is that it does not work, although it should. > > This appears to be the proper fix. > > commit cc050fd3218c4ee467dfe6c234867d84bd3e7119 > Author: Akim Demaille <[email protected]> > Date: Thu Nov 22 18:03:12 2018 +0100 > > warning: avoid warnings about unreachable code > > [...] _______________________________________________ [email protected] https://lists.gnu.org/mailman/listinfo/help-bison