From 9e1595e6e4c31ebfecd1c4c9f833e39799560963 Mon Sep 17 00:00:00 2001 From: Fred Drake Date: Fri, 7 Mar 2003 15:02:03 +0000 Subject: [PATCH] Minor clarification about the ob_size field. --- Doc/api/newtypes.tex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/Doc/api/newtypes.tex b/Doc/api/newtypes.tex index d9f0f06d95e7..b7014c407081 100644 --- a/Doc/api/newtypes.tex +++ b/Doc/api/newtypes.tex @@ -461,9 +461,9 @@ Foo_Type.ob_type = &PyType_Type; example, long ints use a negative \member{ob_size} to indicate a negative number, and N is \code{abs(\member{ob_size})} there. Also, the presence of an \member{ob_size} field in the instance layout - doesn't mean that the type is variable-length (for example, the list - type has fixed-length instances, yet those instances have a - meaningful \member{ob_size} field). + doesn't mean that the instance structure is variable-length (for + example, the structure for the list type has fixed-length instances, + yet those instances have a meaningful \member{ob_size} field). The basic size includes the fields in the instance declared by the macro \csimplemacro{PyObject_HEAD} or -- 2.47.3