-
Notifications
You must be signed in to change notification settings - Fork 58
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
C global constant variable name collision #286
Comments
Hi, Thank you for your detailed feedback and suggestions regarding the asn1scc arguments and the naming conflicts you've encountered. I agree that extending the --type-prefix argument to include global, constant variables seems like a viable solution. However, this change could potentially break existing code that relies on the current naming conventions. @maxime-esa, could you please share your thoughts on this matter? If we proceed with this update, we'll need to consider its impact on existing users. Do you think we should implement this change? |
@usr3-1415 that would indeed break existing code (in C), so I do not think it is a good thing to add this option without any mean to disable it. Alternatively, a new All types and constants would be prefixed the module name ( However this would probably complicate the String templates quite a bit. |
Hi
I am using asn1scc with following arguments:
Types as well as function names are prefixed with
pp_
which solves names conflicts I have due to similarity between two devices asn1 codes. However I still get one name collision between global variables:Related *.asn1
Generated header file
Two issues:
--type-prefix
--type-prefix
help message to include information, that function names are prefixed tooBest regards
The text was updated successfully, but these errors were encountered: