Re: Bison 3.8.2 glr2.cc portability report

Tom,

> Le 10 oct. 2021 =C3=A0 21:37, Tom Shields =
<[email protected]> a =C3=A9crit :
>=20
> I actually haven=E2=80=99t changed the Ox parser specs to use separate =
namespaces for each parser yet, although that is on my list of things to =
do for Ox 1.10.1.  It may be that the warnings will vanish when I make =
this change.  I=E2=80=99ll let you know if shifting to separate =
namespaces makes any difference.

It won't make any difference: the problem is that I use unnamed =
namespaces, not that you didn't define several namespaces.

I used unnamed namespaces precisely so that you could use one namespace =
for several parsers.  And I think it's ok to stay this way.

But if we require different (bison) namespaces, then we could do without =
the unnamed namespace. Yet I think this would be a regression for the =
linker's point of view.=