-
Notifications
You must be signed in to change notification settings - Fork 211
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
Modified name for common types macro scope. #337
Modified name for common types macro scope. #337
Conversation
Not that its mattrers much but maybe convert to uppercase in the template use of the scope_name? |
Yeah i was thinking about that and i wanted to let it on user. User can use upper case in his definition. |
Well two points about that:
|
Well make sense. But i need distuinguish between annotation value and program name and use upper case only when annotation was not used. |
Got it. As I mentioned, I lack the system wide view and impacts. Thank you! |
@Diagano i decided to do it as you proposed. UpperCase. It is because the macro name is still with eRPC prefix and users shouldn't use it and be aware of its existention. Will see future requests :D |
768a13c
to
8587ba5
Compare
@MichalPrincNXP what do you think about this PR? |
Signed-off-by: Cervenka Dusan <cervenka@acrios.com>
Signed-off-by: Cervenka Dusan <cervenka@acrios.com>
8587ba5
to
b073a3d
Compare
I agree with the approach. There are some build fails after the rebase however: erpcgen/src/Generator.cpp:98:14: error: 'transform' is not a member of 'std' Probably, the #include "algorithm" will be needed. |
Signed-off-by: Cervenka Dusan <cervenka@acrios.com>
Thank you. |
Signed-off-by: Cervenka Dusan cervenka@acrios.com
Pull request
Choose Correct
Describe the pull request
Description #336
Default change from ERPC_TYPE_DEFINITIONS to ERPC_TYPE_DEFINITIONS_erpcShim
Default with program name change from ERPC_TYPE_DEFINITIONS to ERPC_TYPE_DEFINITIONS_
Using annotation value for
@scope_name
change from ERPC_TYPE_DEFINITIONS to ERPC_TYPE_DEFINITIONS_To Reproduce
See tests
Expected behavior
See tests
Screenshots
Desktop (please complete the following information):
Steps you didn't forgot to do
Additional context