Command line options for control over debug code generation #154
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds a finer grain of control over debug code generation by adding several new command line options. The existing meaning of
-e,-ex,-exx,-gis not changed.For reference, see discussion at How to do -g but without assertions?
[changed]
[added]
__FB_DEBUG__Comparison to existing options:
-gis same as before, implies-edebug,-edebuginfo,-eassert-eis same as before-exis same as before, implies-e-exxis same as before, implies-e,-ex,-earray,-enullptr,-elocationUnrelated to debug code generation, skeleton code is provided to help user determine how fbc is built and expected defaults:
-help -vgives verbose help-version -vgives verbose version information