From 55c04efb716f1a5d090e1077088de933d0d9735d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Martin=20v=2E=20L=C3=B6wis?= Date: Thu, 27 Jan 2011 21:16:50 +0000 Subject: [PATCH] Changes from David Malcolm: Clarify representation of optional fields; add gdb section. --- pep-0393.txt | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/pep-0393.txt b/pep-0393.txt index 5e121ba6f..41902b3e7 100644 --- a/pep-0393.txt +++ b/pep-0393.txt @@ -83,7 +83,9 @@ These fields have the following interpretations: All three representations are optional, although the str form is 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 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. +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 =========