From: Fred Drake <fdrake@acm.org>
Date: Fri, 7 Mar 2003 15:02:03 +0000 (+0000)
Subject: Minor clarification about the ob_size field.
X-Git-Tag: v2.3c1~1540
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=9e1595e6e4c31ebfecd1c4c9f833e39799560963;p=thirdparty%2FPython%2Fcpython.git

Minor clarification about the ob_size field.
---

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