Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

bazel rules_bison is pretty old #314

Open
dabrahams opened this issue Feb 28, 2021 · 2 comments
Open

bazel rules_bison is pretty old #314

dabrahams opened this issue Feb 28, 2021 · 2 comments
Assignees
Labels
inactive Issues and PRs which have been inactive for at least 90 days.

Comments

@dabrahams
Copy link

dabrahams commented Feb 28, 2021

Note: this is not really a problem. If you have the time to explain why my attempt to point at bison-3.7.5 didn't work, that would be great. Otherwise feel free to close.

The executable semantics code is full of pointers and low-level haxx in part because nobody knew about
https://www.gnu.org/software/bison/manual/html_node/C_002b_002b-Bison-Interface.html or https://www.gnu.org/software/bison/manual/html_node/C_002b_002b-Variants.html

But using those requires a much newer version of Bison than v3.3.x that is supported by the existing rules_bisonActually v3.3.2 has the necessary features. I was seeing errors for other reasons
I attempted to make my own update that included the new version but bazel merrily kept using the earlier version.

See chandlerc/rules_bison@master...dabrahams:bison-3.7.5
and https://github.com/dabrahams/carbon-lang/compare/existential-handroll...dabrahams:modern-bison?expand=1

Perhaps @chandlerc can help
/cc @jsiek

@dabrahams dabrahams changed the title bazel rules_bison is too outdated to support C++ variants bazel rules_bison is pretty old Feb 28, 2021
@geoffromer
Copy link
Contributor

Switching to at least Bison 3.7 would enable us to use -Wcounterexamples, which could be pretty handy.

@github-actions
Copy link

We triage inactive PRs and issues in order to make it easier to find active work. If this issue should remain active or becomes active again, please comment or remove the inactive label. The long term label can also be added for issues which are expected to take time.
This issue is labeled inactive because the last activity was over 90 days ago.

@github-actions github-actions bot added the inactive Issues and PRs which have been inactive for at least 90 days. label Jul 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
inactive Issues and PRs which have been inactive for at least 90 days.
Projects
None yet
Development

No branches or pull requests

3 participants