> Le 20 nov. 2018 à 23:18, Akim Demaille 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
> intentiona
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 wante
Well... for flex 2.6.4 goes away when replacing `%option noyywrap` for
a real `int _wrap(void) { return 1; }`. So that’s an easy workaround
if those warnings where blockers. But I think the `%option` should prevent
such thing from popping up.
> On 25 Nov 2018, at 17:39, Uxio Prego wrote:
>
>
