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 #33
Comments
We won't be changing names of things unless they were to present some real-world problems. (And the names do fit other conventions we've got within Netmail, for good or bad.) That's interesting to know, though! |
How do you think about to avoid that this software depends on undefined behaviour? |
Can you point to any use case where this causes build or runtime errors? If we're going to rename things, I want it to solve a real problem that someone is having. |
When will undefined behaviour become "a real problem" in your software? |
On 09/17/14 12:52, Markus Elfring wrote:
The undefined behavior you mention appears to be a C++ issue. We do not |
Would you like to reconsider your standard interpretation? |
On 09/17/14 13:14, Markus Elfring wrote:
The previous links you sent where specific to C++. This link is more I have not ruled out making a change. Still thinking about how to do it |
I would like to point out that identifiers like "
__WJEBool
" and "_WJROpenDocument
" do 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: