Add -fprefix as an option #170
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
This change is similar to osmocom/asn1c@aa37b8c but implemented differently. For better interoperability it will be good to add support for |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Adds an optional argument
-fprefix=<PREFIX>to the compiler, allowing the user to specify a prefix to be added to generated types.This is a rather useful feature in applications which need to use different ASN.1 definitions with identical names.
The functionality was already there, though was undocumented. It could be used by setting the environment variable
ASN1C_PREFIX.I've left the environment variable setting still possible, however the new optional argument takes precedence.