mirrors
/
cpython
mirror of https://github.com/python/cpython.git
2
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

bpo-46541: Add a Comment About When to Use _Py_DECLARE_STR(). (gh-32063) 

In a gh-32003 comment, I realized it wasn't very clear how _Py_DECLARE_STR() should be used.  This changes adds a comment to clarify.

https://bugs.python.org/issue46541
This commit is contained in:
Eric Snow 2022-03-23 09:52:50 -06:00 committed by GitHub
parent 0360e9f346
commit 21412d037b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Include/internal/pycore_global_strings.h
View File

@ -372,6 +372,16 @@ struct _Py_global_strings {
#define _Py_STR(NAME) \ #define _Py_STR(NAME) \
(_Py_SINGLETON(strings.literals._ ## NAME._ascii.ob_base)) (_Py_SINGLETON(strings.literals._ ## NAME._ascii.ob_base))
/* _Py_DECLARE_STR() should precede all uses of _Py_STR() in a function.
This is true even if the same string has already been declared
elsewhere, even in the same file. Mismatched duplicates are detected
by Tools/scripts/generate-global-objects.py.
Pairing _Py_DECLARE_STR() with every use of _Py_STR() makes sure the
string keeps working even if the declaration is removed somewhere
else. It also makes it clear what the actual string is at every
place it is being used. */
#define _Py_DECLARE_STR(name, str) #define _Py_DECLARE_STR(name, str)
#ifdef __cplusplus #ifdef __cplusplus