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

add a %no_suppress_warnings directive #1027

Merged
merged 6 commits into from
Jan 6, 2023
Merged

add a %no_suppress_warnings directive #1027

merged 6 commits into from
Jan 6, 2023

Conversation

lsf37
Copy link
Member

@lsf37 lsf37 commented Jan 6, 2023

The directive causes the @SuppressWarnings("fallthrough") annotation to be omitted, enabling users to provide their own annotations.

This should allow the scenario in #762 to work.

Char classes still need to be mutable at this point. They can only be
made immutable after the semantic analysis phase at the end of parsing.
By default JFlex emits @SuppressWarnings("fallthrough") at the class
level. This directive removes that annotation and leaves it up to the
user to define their own.

Fixes #762
@lsf37 lsf37 added the enhancement Feature requests label Jan 6, 2023
@lsf37 lsf37 added this to the 1.9.0 milestone Jan 6, 2023
@lsf37 lsf37 self-assigned this Jan 6, 2023
Looks like BUILD.bzl wasn't picked up; renamed to BUILD.bazel and fixed
output drift.
- LexScan.java: uncaught-number-format-exception:
  Format is checked by the lexer spec.

- LexScan.java: misleading-indentation: in comment only.
@lsf37 lsf37 merged commit e2f5d00 into master Jan 6, 2023
@lsf37 lsf37 deleted the fallthrough branch January 6, 2023 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Feature requests
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant