Changes from David Malcolm: Clarify representation of
optional fields; add gdb section.
This commit is contained in:
parent
1259b356bc
commit
55c04efb71
11
pep-0393.txt
11
pep-0393.txt
|
@ -83,7 +83,9 @@ These fields have the following interpretations:
|
||||||
|
|
||||||
All three representations are optional, although the str form is
|
All three representations are optional, although the str form is
|
||||||
considered the canonical representation which can be absent only
|
considered the canonical representation which can be absent only
|
||||||
while the string is being created.
|
while the string is being created. If the representation is absent,
|
||||||
|
the pointer is NULL, and the corresponding length field may contain
|
||||||
|
arbitrary data.
|
||||||
|
|
||||||
The Py_UNICODE type is still supported but deprecated. It is always
|
The Py_UNICODE type is still supported but deprecated. It is always
|
||||||
defined as a typedef for wchar_t, so the wstr representation can double
|
defined as a typedef for wchar_t, so the wstr representation can double
|
||||||
|
@ -165,6 +167,13 @@ Stable ABI
|
||||||
|
|
||||||
None of the functions in this PEP become part of the stable ABI.
|
None of the functions in this PEP become part of the stable ABI.
|
||||||
|
|
||||||
|
GDB Debugging Hooks
|
||||||
|
-------------------
|
||||||
|
Tools/gdb/libpython.py contains debugging hooks that embed knowledge
|
||||||
|
about the internals of CPython's data types, include PyUnicodeObject
|
||||||
|
instances. It will need to be slightly updated to track the change.
|
||||||
|
|
||||||
|
|
||||||
Copyright
|
Copyright
|
||||||
=========
|
=========
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue