-
-
Notifications
You must be signed in to change notification settings - Fork 31
Issue #21: Avoid C++ keyword module
#22
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM with easy solution but let's wait @vstinner 's review
Is it possible to detect the error using a C++ compiler warning to prevent adding new ones? The C++ compatibility is tested in tests/. |
Good point. I'll add a test. |
I guess that this PR is related to: https://bugs.python.org/issue39355 I don't get any warning:
|
I changed my mind. Python.h has the issue, so until Python will be fixed ( https://bugs.python.org/issue39355 https://bugs.python.org/issue39355 ) we cannot test it in pythoncapi_compat.h which includes Python.h. I don't want to add a test using a regex which would emit false alarm if the word "module" is used in a comment. |
Thanks, I merged your fix! |
Makes sense! |
This reverts commit ca6a60e.
Rename
module
variable/argument names asmod
.Fixes #21