On Mon, Oct 29, 2012 at 4:39 PM, Andrew Robinson <andr...@r3dsolutions.com> wrote: > In addition to those items you mention, of which the reference count is not > even *inside* the struct -- there is additional debugging information not > mentioned. Built in objects contain a "line number", a "column number", and > a "context" pointer. These each require a full word of storage. > > Also, built in types appear to have a "kind" field which indicates the > object "type" but is not a pointer. That suggests two "object" type > indicators, a generic pointer (probably pointing to "builtin"? somewhere > outside the struct) and a specific one (an enum) inside the "C" struct. > > Inside the tuple struct, I count 4 undocumented words of information. > Over all, there is a length, the list of pointers, a "kind", "line", "col" > and "context"; making 6 pieces in total. > > Although your comment says the head pointer is not required; I found in > 3.3.0 that it is a true head pointer; The Tuple() function on line 2069 of > Python-ast.c, (3.3 version) -- is passed in a pointer called *elts. That > pointer is copied into the Tuple struct.
As above, you're looking at the compiler code, which is why you're finding things like "line" and "column". The tuple struct is defined in tupleobject.h and stores tuple elements in a tail array. > How ironic, slices don't have debugging info, that's the main reason they > are smaller. > When I do slice(3,0,2), suprisingly "Slice()" is NOT called. > But when I do a[1:2:3] it *IS* called. Because compiling the latter involves parsing slicing syntax, and compiling the former does not. :-) -- http://mail.python.org/mailman/listinfo/python-list
