Request for latest release #103
Comments
|
+1 |
1 similar comment
|
+1 |
|
bump |
|
For now, we post-process the generated |
|
bump again |
|
+1 |
|
+1...? |
Yeah same issue, it led to mdbtools/mdbtools#425... |
|
+1 |
|
I emailed [email protected] on 27 June, but have not yet received a response. |
Ah yes, so I see: https://lists.gnu.org/archive/html/bug-bison/2024-06/msg00000.html Also, more recently than that, I see @ArsenArsen submitted a patch to bison-patches that hasn't received a response yet, either: https://lists.gnu.org/archive/html/bison-patches/2024-07/msg00000.html |
|
might be worthwhile to email [email protected] with an inquiry.. bison is currently marked as looking for co-maintainers. now, I don't know enough parsing theory to step up (plus I also have lots of other commitments), but I invite folk to take up that offer and email the address above |
Bison in 3.8.2 added new warnings to catch m4 strings accidentally included in the generated code output. It had the unfortunate side effect of flagging grammars that include "m4_foo" style strings as identifiers in their grammar (which we do). Based on the thread, it looks like a fix was implemented on the Bison side, but as of three years later, no release has been made. Bison seems to possibly have maintainer inactivity: akimd/bison#103. Since a fix for the false positive is not forthcoming, disable the warning. Unfortunately, I don't think a more granular disablement is available, but IMO false positive warnings are worse than false negatives.
Bison in 3.8.2 added new warnings to catch m4 strings accidentally included in the generated code output. It had the unfortunate side effect of flagging grammars that include "m4_foo" style strings as identifiers in their grammar (which we do). Based on the thread, it looks like a fix was implemented on the Bison side, but as of three years later, no release has been made. Bison seems to possibly have maintainer inactivity: akimd/bison#103. Since a fix for the false positive is not forthcoming, disable the warning. Unfortunately, I don't think a more granular disablement is available, but IMO false positive warnings are worse than false negatives.
I am facing this issue #89 using the latest available bision
3.8.2. It seems it is fixed in the current master branch, but is not yet available with the release version. The most recent release available is from September 2021. I would like to request if you could make a new release. Thank you for your time and consideration.The text was updated successfully, but these errors were encountered: