On Wed, 2019-05-22 at 18:06 +0200, Akim Demaille wrote:
Hi Erik,
Le 22 mai 2019 à 08:54, Erik Faye-Lund <
address@hidden> a écrit :
I ended up reverting the change [from-%error-verbose to %define
parse.error verbose] , and I can't find an obcious way to
support both old and new versions with the same source file.
Well, you just disable warnings about deprecated features.
-Wno-deprecated.
The Android SDK also ships a pre-3.x version of Bison, so you're
not
the only one affected. Also, Chocolatey doesn't provide a new
enough
version of Bison for Windows either.
I would be interested in knowing why some distros lag. Do you
happen to know why for some of them?
The only clear examples I know of are the Android SDK and Chocolatey.
As I said before, we mighit not have to use the bison version shipped
in the Android SDK, so perhaps that's fixable. And for Chocolatey, it
turns out they have a winflexbison pacakge and a winflexbison3 package,
and the latter has a more recent Bison version.
So looking at this again, it looks like it might be solveable, at least
in the cases where this is visible to me.
Brian: do you think VMWare cuold upgrade the Bison version used in the
forseeable future?