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

Not all the command line options are exposed through the plugin. #20

Closed
dilipbiswal opened this issue Mar 1, 2019 · 3 comments
Closed

Comments

@dilipbiswal
Copy link
Contributor

dilipbiswal commented Mar 1, 2019

Here are the lists of command line options.

$ antlr4
ANTLR Parser Generator Version 4.0b3
-o <arg>                specify output directory where all output is generated
-lib <arg>              specify location of grammars, tokens files
-atn                    generate rule augmented transition network diagrams
-encoding <arg>         specify grammar file encoding; e.g., euc-jp
-message-format <arg>   specify output style for messages in antlr, gnu, vs2005
-listener               generate parse tree listener (default)
-no-listener            don't generate parse tree listener
-visitor                generate parse tree visitor
-no-visitor             don't generate parse tree visitor (default)
-package <arg>          specify a package/namespace for the generated code
-depend                 generate file dependencies
-D<option>=value        set/override a grammar-level option
-Werror                 treat warnings as errors
-Xsave-lexer            save temp lexer file created for combined grammars
-XdbgST                 launch StringTemplate visualizer on generated code
-Xforce-atn             use the ATN simulator for all predictions
-Xlog                   dump lots of logging info to antlr-timestamp.log
-XdbgSTWait             wait for STViz to close before continuing

I want to be able to turn warnings to errors while generating parser. But that option is not exposed through the plugin ? The maven plugin for antlr4 allows us to do that.

cc @ihji

@ihji
Copy link
Owner

ihji commented Mar 8, 2019

@dilipbiswal Thanks for opening the issue. I expect I can work on it next week. I'm also more than happy to merge PR if it's urgent.

@dilipbiswal
Copy link
Contributor Author

@ihji Thanks for your response. I have tried to create two prs. One for sbt-1.0 and other for sbt-013.

@ihji
Copy link
Owner

ihji commented Mar 11, 2019

published 0.8.2 (sbt-1.0) and 0.7.13 (sbt-0.13). Thanks!

@ihji ihji closed this as completed Mar 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants