iSharkFly-Open
/
python-peps
mirror of https://github.com/python/peps.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

PEP 539: Fix wording about Py_tss_NEEDS_INIT (#436) 

Make more sense to replace the word "default value" with
"initializer" for Py_tss_NEEDS_INIT.
This commit is contained in:
Masayuki Yamamoto 2017-10-24 21:58:39 +09:00 committed by Nick Coghlan
parent 55504a85a6
commit 370be4c92a
1 changed files with 3 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
pep-0539.txt
View File

@ -70,8 +70,7 @@ The specification also adds a few new features:
where ``NATIVE_TSS_KEY_T`` is a macro whose value depends on the where ``NATIVE_TSS_KEY_T`` is a macro whose value depends on the
underlying native TLS implementation (e.g. ``pthread_key_t``). underlying native TLS implementation (e.g. ``pthread_key_t``).
* A constant default value for ``Py_tss_t`` variables, * An initializer for ``Py_tss_t`` variables, ``Py_tss_NEEDS_INIT``.
``Py_tss_NEEDS_INIT``.
* Three new functions:: * Three new functions::
@ -157,7 +156,7 @@ Features - create key - create key
key key
- check key's initialization - check key's initialization
state state
Default Value (``-1`` as key creation ``Py_tss_NEEDS_INIT`` Key Initializer (``-1`` as key creation ``Py_tss_NEEDS_INIT``
failure) failure)
Requirement native threads native threads Requirement native threads native threads
(since CPython 3.7 [9]_) (since CPython 3.7 [9]_)
@ -287,7 +286,7 @@ part of the C11 threads API [15]_. However, this is in no way meant to imply
compatibility with or support for the C11 threads API, or signal any future compatibility with or support for the C11 threads API, or signal any future
intention of supporting C11--it's just the influence for the naming and design. intention of supporting C11--it's just the influence for the naming and design.
The inclusion of the special default value ``Py_tss_NEEDS_INIT`` is required The inclusion of the special initializer ``Py_tss_NEEDS_INIT`` is required
by the fact that not all native TLS implementations define a sentinel value by the fact that not all native TLS implementations define a sentinel value
for uninitialized TLS keys. For example, on Windows a TLS key is for uninitialized TLS keys. For example, on Windows a TLS key is
represented by a ``DWORD`` (``unsigned int``) and its value must be treated represented by a ``DWORD`` (``unsigned int``) and its value must be treated