Bison version 2.2 has been released.
To make GPC work with it requires some minor changes. Patch attached, details in the ChangeLog entry.
Bison 2.2 also has a new feature:
: * %require "VERSION" : This specifies that the grammar file depends on features implemented : in Bison version VERSION or higher.
Since we actively use some newer (2.0 and/or 2.1) features of Bison, we actually should use this check, to avoid users even trying with older Bisons which cannot work. OTOH, since the check is new in 2.2, we can't "%require 2.1", so by using this check we would needlessly (ATM) require Bison 2.2.
What should we do? Perhaps wait until 2.2 is more widespread, then require it?
Frank
I wrote:
Bison 2.2 also has a new feature:
: * %require "VERSION" : This specifies that the grammar file depends on features implemented : in Bison version VERSION or higher.
Since we actively use some newer (2.0 and/or 2.1) features of Bison, we actually should use this check, to avoid users even trying with older Bisons which cannot work. OTOH, since the check is new in 2.2, we can't "%require 2.1", so by using this check we would needlessly (ATM) require Bison 2.2.
What should we do? Perhaps wait until 2.2 is more widespread, then require it?
Of course, there's also this bug in previous Bisons, leading to a parser crash the Chief observed, that Waldek fixed for 2.2. This would suggest to upgrade to Bison 2.2 sooner rather than later. Still, by adding a "%require" directive, we would force users to upgrade (only those who actually rebuild the Bison file at all, though, i.e. not for a normal GPC build).
Frank
Frank Heckenbach wrote:
I wrote:
Bison 2.2 also has a new feature:
: * %require "VERSION" : This specifies that the grammar file depends on features implemented : in Bison version VERSION or higher.
Since we actively use some newer (2.0 and/or 2.1) features of Bison, we actually should use this check, to avoid users even trying with older Bisons which cannot work. OTOH, since the check is new in 2.2, we can't "%require 2.1", so by using this check we would needlessly (ATM) require Bison 2.2.
What should we do? Perhaps wait until 2.2 is more widespread, then require it?
Of course, there's also this bug in previous Bisons, leading to a parser crash the Chief observed, that Waldek fixed for 2.2. This would suggest to upgrade to Bison 2.2 sooner rather than later. Still, by adding a "%require" directive, we would force users to upgrade (only those who actually rebuild the Bison file at all, though, i.e. not for a normal GPC build).
Since it is generally available, I don't mind to (be forced to) upgrade to Bison 2.2.
Regards,
Adriaan van Os
On 20 May 2006 at 3:15, Frank Heckenbach wrote:
Bison version 2.2 has been released.
To make GPC work with it requires some minor changes. Patch attached, details in the ChangeLog entry.
Bison 2.2 also has a new feature:
: * %require "VERSION" : This specifies that the grammar file depends on features implemented : in Bison version VERSION or higher.
Since we actively use some newer (2.0 and/or 2.1) features of Bison, we actually should use this check, to avoid users even trying with older Bisons which cannot work. OTOH, since the check is new in 2.2, we can't "%require 2.1", so by using this check we would needlessly (ATM) require Bison 2.2.
What should we do? Perhaps wait until 2.2 is more widespread, then require it?
I don't see any problem with this. Anyone who wants to build a compiler should also be able to build bison!
Best regards, The Chief -------- Prof. Abimbola A. Olowofoyeku (The African Chief) web: http://www.greatchief.plus.com/
Prof A Olowofoyeku (The African Chief) wrote:
On 20 May 2006 at 3:15, Frank Heckenbach wrote:
Bison version 2.2 has been released.
Bison 2.2 also has a new feature:
: * %require "VERSION" : This specifies that the grammar file depends on features implemented : in Bison version VERSION or higher.
Since we actively use some newer (2.0 and/or 2.1) features of Bison, we actually should use this check, to avoid users even trying with older Bisons which cannot work. OTOH, since the check is new in 2.2, we can't "%require 2.1", so by using this check we would needlessly (ATM) require Bison 2.2.
What should we do? Perhaps wait until 2.2 is more widespread, then require it?
I don't see any problem with this. Anyone who wants to build a compiler should also be able to build bison!
Bison version 2.3 has been released now. I've tested that GPC with my Bison-2.2 patch works well with 2.3, too. Since it's mainly a bugfix release for 2.2 (though AFAICS the bugs didn't directly affect GPC), I think we should require 2.3 then, as we probably shouldn't invite people to install 2.2 now.
Frank
Frank Heckenbach wrote:
Bison version 2.3 has been released now. I've tested that GPC with my Bison-2.2 patch works well with 2.3, too. Since it's mainly a bugfix release for 2.2 (though AFAICS the bugs didn't directly affect GPC), I think we should require 2.3 then, as we probably shouldn't invite people to install 2.2 now.
Requiring bison 2.3 is OK for me.
Regards,
Adriaan van Os