-
Notifications
You must be signed in to change notification settings - Fork 27
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
reserved identifier violation #2
Comments
Thank you for your advice. |
How do you think about to rename also functions? |
Thanks for your renaming of affected identifiers. 🔮 Can a name selection trigger any corresponding software development concerns? |
I don't want to rename them anymore.
Sorry, I couldn't understand what you mean. |
This implementation detail can be fine according to the naming convention for the programming language “C”.
Is there a possibility that an identifier will be constructed (together with the prefix “PCC_INCLUDED_”) that does not result in an acceptable include guard? |
Identifiers ending with "_t" are also reserved in C++. I see many instances of this in packcc, even in the develop branch. https://stackoverflow.com/a/228797/ I also see "__pcc_in", "__pcc_out", and "__pcc_ctx" in the develop branch, all of which C++ considers to be reserved identifiers due to the leading double underscores. As @elfring says, C++ has stricter rules than C regarding which identifiers are considered reserved. |
Is this a parser generator for C or C++? |
Just for C. |
Why @elfring asked you to comply with C++ language standard then? |
@elfring, @MaxBarraclough,
If you have any objection against closing this issue, let me know by the end of this month (Aug. 2022). |
💭 I became curious if interests could grow further for involved standard compliance aspects. |
Why not putting some ads on Youtube instead of violating the scope of this project? |
Some development concerns can be tackled together for the programming languages “C” and “C++”, can't they? |
It might be just your impression, and isn't persuasive.
I never deny using C and C++ together. |
I would like to point out that identifiers like “
PCC_INCLUDED__
” and “STRING_FLAG__IDENTIFIER
” do eventually not fit to the expected naming convention of the C++ language standard.Would you like to adjust your selection for unique names?
The text was updated successfully, but these errors were encountered: