[issue35671] reserved identifier violation

Ronald Oussoren added the comment: (changed the type from "security" because this is not a security incident). Both ISO C and C++ define "reserved identifiers" that are reserved for the implementation and where use in programs is undefined behaviour. However, these definitions reserve *all*

[issue35671] reserved identifier violation

Markus Elfring added the comment: * How do you think about to reduce the tampering with the reserved name space in mentioned source code (and also in related components)? * Would you like to avoid that this software depends on undefined behaviour? -- _

[issue35671] reserved identifier violation

STINNER Victor added the comment: __DYNAMIC_ANNOTATIONS_H__ can be replaced with PY_DYNAMIC_ANNOTATIONS_H. I don't understand why _Py_memory_order and only _Py_memory_order is a problem. We have tons of symbols starting with _Py: functions, defines, variables, etc. -- __

[issue35671] reserved identifier violation

Ronald Oussoren added the comment: See: Basically all names starting with double underscores are reserved for the implementation in C++. Likewise for all names starting with an undersc

[issue35671] reserved identifier violation

STINNER Victor added the comment: Hi, I'm sorry but I don't understand your problem. Are you trying to build Python using C++? If yes, do you get a compilation error? I'm not sure that it's supported. Or do you try to build a C extension for Python using a C++ compiler? --

[issue35671] reserved identifier violation

Change by Raymond Hettinger : -- nosy: +vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https://mail

[issue35671] reserved identifier violation

New submission from Markus Elfring : I would like to point out that identifiers like “__DYNAMIC_ANNOTATIONS_H__” and “_Py_memory_order” do not fit to the expected naming convention of the C++ language standard. https://www.securecoding.cert.org/confluence/display/cplusplus/DCL51-CPP.+Do+not+dec