Re: [PATCH 00/14] glr2.cc: fix linking conflicts

Thomas Shields <[email protected]> Mon, 13 Sep 2021 09:19:46 -0500
Newsgroups gmane.comp.parsers.bison.patches
Message-ID <[email protected]>
Hans,

Thanks for the note.

I should have mentioned that the version of Ox I was reporting against is 1.=
10 (under development, I=E2=80=99m the only developer).

I=E2=80=99m in the process of =E2=80=9Cupgrading=E2=80=9D the Ox source from=
 C to C++, allowing me to simplify the Ox implementation.

Akim=E2=80=99s patches fix some problems I reported when I switched the Ox p=
arser specs to use the Bison C++ skeleton, and also switched from the legacy=
 =E2=80=98%union=E2=80=99 to Bison=E2=80=99s =E2=80=98%define api.value.type=
 variant=E2=80=99 directive.

Once I get through the initial cleanup effort (replacing malloc, calloc, rea=
lloc, free, strdup, & strndup; converting to use C++ library containers; and=
 rewriting the output manager) and get Ox through the portability tests (on L=
inux, Solaris & Windows), I=E2=80=99ll release 1.10. It will probably take m=
e another week to get through this.

Regards,

Tom Shields

Sent from Tom's iDevice

> On Sep 13, 2021, at 8:29 AM, Hans =C3=85berg <[email protected]> wrote:
> =EF=BB=BF
>> On 13 Sep 2021, at 07:29, Akim Demaille <[email protected]> wrote:
>>=20
>> Hi Tom,
>>=20
>>> Le 12 sept. 2021 =C3=A0 20:50, Tom Shields a =C3=A9crit :
>>> Akim,
>>> The Ox attribute grammar evaluator generator compiles, links, and passes=
 its regression tests under macOS Big Sur (v11.5.2) using this version of Bi=
son with the following C++ compilers:
>>> - Xcode (12.5.1): g++ reports its version as =E2=80=98Apple clang versio=
n 12.0.5 (clang-1205.0.22.11)
>>> - GNU (Homebrew): g++ reports its version as =E2=80=98Homebrew GCC 11.2.=
0) 11.1.0=E2=80=99
>>> - LLVM (Homebrew): clang++ reports it version as =E2=80=98Homebrew clang=
 version 12.0.1'
>>=20
>> Wonderful news, thanks a lot!
>=20
> With Ox 1.9.3 and gcc (MacPorts gcc11 11.2.0_1) 11.2.0 on the same platfor=
m, make check passes (the OP did not mention the version, and I was not awar=
e of that it is being developed).