-
Notifications
You must be signed in to change notification settings - Fork 284
Add message for unknown cbmc option #1058
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
Conversation
|
See #910 for comments. |
b85055e to
7035ea1
Compare
|
@peterschrammel @tautschnig this is ready for your review. |
mgudemann
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
tautschnig
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
|
@tautschnig Yes both PRs are identical and all your comments have been addressed. |
tautschnig
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks a lot for the info!
|
I think this has already been included into master (via a prior merge I guess). Rebasing the PR on develop resulted in noop. Is it OK to drop this PR @tautschnig? |
|
Re-targeted to master. |
During command line parsing, if an unknown option is read, store it and output an error message at parse_options_baset::main Add regression tests to check the feature.
7035ea1 to
7332fb8
Compare
|
@peterschrammel Can I close this? It's been in test-generator for a year now and it seems to have been integrated into jbmc in the meantime: |
|
If it is already in |
|
Verified already in cbmc/develop. |
During command line parsing, if an unknown option is read, store it and output an error message at
parse_options_baset::main.This adds a message when the command line parser finds an unknown option. Ideally, this should be done using the
messagetframework, butparse_options_basetdoes not inherit from it. All messages produced in this context are directly sent to the standard (as for the help string) or the error outputs.