1993-07-28 17:05:47 +08:00
|
|
|
#ifndef Py_OBJECT_H
|
|
|
|
#define Py_OBJECT_H
|
|
|
|
#ifdef __cplusplus
|
|
|
|
extern "C" {
|
|
|
|
#endif
|
|
|
|
|
1991-02-19 20:39:46 +08:00
|
|
|
|
1990-10-14 20:07:46 +08:00
|
|
|
/* Object and type object interface */
|
|
|
|
|
|
|
|
/*
|
|
|
|
Objects are structures allocated on the heap. Special rules apply to
|
|
|
|
the use of objects to ensure they are properly garbage-collected.
|
|
|
|
Objects are never allocated statically or on the stack; they must be
|
|
|
|
accessed through special macros and functions only. (Type objects are
|
|
|
|
exceptions to the first rule; the standard types are represented by
|
2002-07-08 03:59:50 +08:00
|
|
|
statically initialized type objects, although work on type/class unification
|
|
|
|
for Python 2.2 made it possible to have heap-allocated type objects too).
|
1990-10-14 20:07:46 +08:00
|
|
|
|
|
|
|
An object has a 'reference count' that is increased or decreased when a
|
|
|
|
pointer to the object is copied or deleted; when the reference count
|
|
|
|
reaches zero there are no references to the object left and it can be
|
|
|
|
removed from the heap.
|
|
|
|
|
|
|
|
An object has a 'type' that determines what it represents and what kind
|
|
|
|
of data it contains. An object's type is fixed when it is created.
|
|
|
|
Types themselves are represented as objects; an object contains a
|
|
|
|
pointer to the corresponding type object. The type itself has a type
|
|
|
|
pointer pointing to the object representing the type 'type', which
|
|
|
|
contains a pointer to itself!).
|
|
|
|
|
|
|
|
Objects do not float around in memory; once allocated an object keeps
|
|
|
|
the same size and address. Objects that must hold variable-size data
|
|
|
|
can contain pointers to variable-size parts of the object. Not all
|
|
|
|
objects of the same type have the same size; but the size cannot change
|
|
|
|
after allocation. (These restrictions are made so a reference to an
|
|
|
|
object can be simply a pointer -- moving an object would require
|
|
|
|
updating all the pointers, and changing an object's size would require
|
|
|
|
moving it if there was another object right next to it.)
|
|
|
|
|
1995-01-12 19:45:45 +08:00
|
|
|
Objects are always accessed through pointers of the type 'PyObject *'.
|
|
|
|
The type 'PyObject' is a structure that only contains the reference count
|
1990-10-14 20:07:46 +08:00
|
|
|
and the type pointer. The actual memory allocated for an object
|
|
|
|
contains other data that can only be accessed after casting the pointer
|
|
|
|
to a pointer to a longer structure type. This longer type must start
|
1995-01-12 19:45:45 +08:00
|
|
|
with the reference count and type fields; the macro PyObject_HEAD should be
|
2000-07-16 20:04:32 +08:00
|
|
|
used for this (to accommodate for future changes). The implementation
|
1990-10-14 20:07:46 +08:00
|
|
|
of a particular object type can cast the object pointer to the proper
|
|
|
|
type and back.
|
|
|
|
|
|
|
|
A standard interface exists for objects that contain an array of items
|
|
|
|
whose size is determined when the object is allocated.
|
|
|
|
*/
|
|
|
|
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
/* Py_DEBUG implies Py_TRACE_REFS. */
|
|
|
|
#if defined(Py_DEBUG) && !defined(Py_TRACE_REFS)
|
1995-01-12 19:45:45 +08:00
|
|
|
#define Py_TRACE_REFS
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
#endif
|
1990-12-20 23:06:42 +08:00
|
|
|
|
2002-07-08 03:59:50 +08:00
|
|
|
/* Py_TRACE_REFS implies Py_REF_DEBUG. */
|
|
|
|
#if defined(Py_TRACE_REFS) && !defined(Py_REF_DEBUG)
|
1995-01-12 19:45:45 +08:00
|
|
|
#define Py_REF_DEBUG
|
2002-07-08 03:59:50 +08:00
|
|
|
#endif
|
1990-10-14 20:07:46 +08:00
|
|
|
|
1995-01-12 19:45:45 +08:00
|
|
|
#ifdef Py_TRACE_REFS
|
2002-07-08 03:59:50 +08:00
|
|
|
/* Define pointers to support a doubly-linked list of all live heap objects. */
|
|
|
|
#define _PyObject_HEAD_EXTRA \
|
|
|
|
struct _object *_ob_next; \
|
|
|
|
struct _object *_ob_prev;
|
|
|
|
|
|
|
|
#define _PyObject_EXTRA_INIT 0, 0,
|
|
|
|
|
|
|
|
#else
|
|
|
|
#define _PyObject_HEAD_EXTRA
|
|
|
|
#define _PyObject_EXTRA_INIT
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/* PyObject_HEAD defines the initial segment of every PyObject. */
|
|
|
|
#define PyObject_HEAD \
|
|
|
|
_PyObject_HEAD_EXTRA \
|
|
|
|
int ob_refcnt; \
|
1990-10-14 20:07:46 +08:00
|
|
|
struct _typeobject *ob_type;
|
|
|
|
|
2002-07-08 03:59:50 +08:00
|
|
|
#define PyObject_HEAD_INIT(type) \
|
|
|
|
_PyObject_EXTRA_INIT \
|
|
|
|
1, type,
|
|
|
|
|
|
|
|
/* PyObject_VAR_HEAD defines the initial segment of all variable-size
|
|
|
|
* container objects. These end with a declaration of an array with 1
|
|
|
|
* element, but enough space is malloc'ed so that the array actually
|
|
|
|
* has room for ob_size elements. Note that ob_size is an element count,
|
|
|
|
* not necessarily a byte count.
|
|
|
|
*/
|
|
|
|
#define PyObject_VAR_HEAD \
|
|
|
|
PyObject_HEAD \
|
1995-01-05 03:06:22 +08:00
|
|
|
int ob_size; /* Number of items in variable part */
|
2002-07-07 13:13:56 +08:00
|
|
|
|
2002-07-08 03:59:50 +08:00
|
|
|
/* Nothing is actually declared to be a PyObject, but every pointer to
|
|
|
|
* a Python object can be cast to a PyObject*. This is inheritance built
|
|
|
|
* by hand. Similarly every pointer to a variable-size Python object can,
|
|
|
|
* in addition, be cast to PyVarObject*.
|
|
|
|
*/
|
1990-10-14 20:07:46 +08:00
|
|
|
typedef struct _object {
|
1995-01-12 19:45:45 +08:00
|
|
|
PyObject_HEAD
|
|
|
|
} PyObject;
|
1990-10-14 20:07:46 +08:00
|
|
|
|
|
|
|
typedef struct {
|
1995-01-12 19:45:45 +08:00
|
|
|
PyObject_VAR_HEAD
|
1997-05-16 05:31:03 +08:00
|
|
|
} PyVarObject;
|
1990-10-14 20:07:46 +08:00
|
|
|
|
|
|
|
|
|
|
|
/*
|
|
|
|
Type objects contain a string containing the type name (to help somewhat
|
2002-07-08 03:59:50 +08:00
|
|
|
in debugging), the allocation parameters (see PyObject_New() and
|
|
|
|
PyObject_NewVar()),
|
|
|
|
and methods for accessing objects of the type. Methods are optional, a
|
1990-10-14 20:07:46 +08:00
|
|
|
nil pointer meaning that particular kind of access is not available for
|
1995-01-12 19:45:45 +08:00
|
|
|
this type. The Py_DECREF() macro uses the tp_dealloc method without
|
1990-10-14 20:07:46 +08:00
|
|
|
checking for a nil pointer; it should always be implemented except if
|
|
|
|
the implementation can guarantee that the reference count will never
|
2002-07-08 03:59:50 +08:00
|
|
|
reach zero (e.g., for statically allocated type objects).
|
1990-10-14 20:07:46 +08:00
|
|
|
|
|
|
|
NB: the methods for certain type groups are now contained in separate
|
|
|
|
method blocks.
|
|
|
|
*/
|
|
|
|
|
2000-07-08 08:32:04 +08:00
|
|
|
typedef PyObject * (*unaryfunc)(PyObject *);
|
|
|
|
typedef PyObject * (*binaryfunc)(PyObject *, PyObject *);
|
|
|
|
typedef PyObject * (*ternaryfunc)(PyObject *, PyObject *, PyObject *);
|
|
|
|
typedef int (*inquiry)(PyObject *);
|
|
|
|
typedef int (*coercion)(PyObject **, PyObject **);
|
|
|
|
typedef PyObject *(*intargfunc)(PyObject *, int);
|
|
|
|
typedef PyObject *(*intintargfunc)(PyObject *, int, int);
|
|
|
|
typedef int(*intobjargproc)(PyObject *, int, PyObject *);
|
|
|
|
typedef int(*intintobjargproc)(PyObject *, int, int, PyObject *);
|
|
|
|
typedef int(*objobjargproc)(PyObject *, PyObject *, PyObject *);
|
|
|
|
typedef int (*getreadbufferproc)(PyObject *, int, void **);
|
|
|
|
typedef int (*getwritebufferproc)(PyObject *, int, void **);
|
|
|
|
typedef int (*getsegcountproc)(PyObject *, int *);
|
|
|
|
typedef int (*getcharbufferproc)(PyObject *, int, const char **);
|
|
|
|
typedef int (*objobjproc)(PyObject *, PyObject *);
|
|
|
|
typedef int (*visitproc)(PyObject *, void *);
|
|
|
|
typedef int (*traverseproc)(PyObject *, visitproc, void *);
|
1994-08-01 19:34:53 +08:00
|
|
|
|
1990-10-14 20:07:46 +08:00
|
|
|
typedef struct {
|
2001-01-17 23:20:39 +08:00
|
|
|
/* For numbers without flag bit Py_TPFLAGS_CHECKTYPES set, all
|
|
|
|
arguments are guaranteed to be of the object's type (modulo
|
2002-07-08 03:59:50 +08:00
|
|
|
coercion hacks -- i.e. if the type's coercion function
|
2001-01-17 23:20:39 +08:00
|
|
|
returns other types, then these are allowed as well). Numbers that
|
|
|
|
have the Py_TPFLAGS_CHECKTYPES flag bit set should check *both*
|
|
|
|
arguments for proper type and implement the necessary conversions
|
|
|
|
in the slot functions themselves. */
|
2001-01-04 09:31:50 +08:00
|
|
|
|
1994-08-01 19:34:53 +08:00
|
|
|
binaryfunc nb_add;
|
|
|
|
binaryfunc nb_subtract;
|
|
|
|
binaryfunc nb_multiply;
|
|
|
|
binaryfunc nb_divide;
|
|
|
|
binaryfunc nb_remainder;
|
|
|
|
binaryfunc nb_divmod;
|
1994-08-09 21:21:54 +08:00
|
|
|
ternaryfunc nb_power;
|
1994-08-01 19:34:53 +08:00
|
|
|
unaryfunc nb_negative;
|
|
|
|
unaryfunc nb_positive;
|
|
|
|
unaryfunc nb_absolute;
|
|
|
|
inquiry nb_nonzero;
|
|
|
|
unaryfunc nb_invert;
|
|
|
|
binaryfunc nb_lshift;
|
|
|
|
binaryfunc nb_rshift;
|
|
|
|
binaryfunc nb_and;
|
|
|
|
binaryfunc nb_xor;
|
|
|
|
binaryfunc nb_or;
|
|
|
|
coercion nb_coerce;
|
|
|
|
unaryfunc nb_int;
|
|
|
|
unaryfunc nb_long;
|
|
|
|
unaryfunc nb_float;
|
|
|
|
unaryfunc nb_oct;
|
|
|
|
unaryfunc nb_hex;
|
2001-08-16 02:32:33 +08:00
|
|
|
/* Added in release 2.0 */
|
2000-08-25 04:09:45 +08:00
|
|
|
binaryfunc nb_inplace_add;
|
|
|
|
binaryfunc nb_inplace_subtract;
|
|
|
|
binaryfunc nb_inplace_multiply;
|
|
|
|
binaryfunc nb_inplace_divide;
|
|
|
|
binaryfunc nb_inplace_remainder;
|
|
|
|
ternaryfunc nb_inplace_power;
|
|
|
|
binaryfunc nb_inplace_lshift;
|
|
|
|
binaryfunc nb_inplace_rshift;
|
|
|
|
binaryfunc nb_inplace_and;
|
|
|
|
binaryfunc nb_inplace_xor;
|
|
|
|
binaryfunc nb_inplace_or;
|
2001-08-08 13:00:18 +08:00
|
|
|
|
2001-08-16 02:32:33 +08:00
|
|
|
/* Added in release 2.2 */
|
2001-08-08 13:00:18 +08:00
|
|
|
/* The following require the Py_TPFLAGS_HAVE_CLASS flag */
|
|
|
|
binaryfunc nb_floor_divide;
|
|
|
|
binaryfunc nb_true_divide;
|
|
|
|
binaryfunc nb_inplace_floor_divide;
|
|
|
|
binaryfunc nb_inplace_true_divide;
|
1995-01-12 19:45:45 +08:00
|
|
|
} PyNumberMethods;
|
1990-10-14 20:07:46 +08:00
|
|
|
|
|
|
|
typedef struct {
|
1994-08-01 19:34:53 +08:00
|
|
|
inquiry sq_length;
|
|
|
|
binaryfunc sq_concat;
|
|
|
|
intargfunc sq_repeat;
|
|
|
|
intargfunc sq_item;
|
|
|
|
intintargfunc sq_slice;
|
|
|
|
intobjargproc sq_ass_item;
|
|
|
|
intintobjargproc sq_ass_slice;
|
2000-02-28 23:00:40 +08:00
|
|
|
objobjproc sq_contains;
|
2001-08-16 02:32:33 +08:00
|
|
|
/* Added in release 2.0 */
|
2000-08-25 04:09:45 +08:00
|
|
|
binaryfunc sq_inplace_concat;
|
|
|
|
intargfunc sq_inplace_repeat;
|
1995-01-12 19:45:45 +08:00
|
|
|
} PySequenceMethods;
|
1990-10-14 20:07:46 +08:00
|
|
|
|
|
|
|
typedef struct {
|
1994-08-01 19:34:53 +08:00
|
|
|
inquiry mp_length;
|
|
|
|
binaryfunc mp_subscript;
|
|
|
|
objobjargproc mp_ass_subscript;
|
1995-01-12 19:45:45 +08:00
|
|
|
} PyMappingMethods;
|
1990-10-14 20:07:46 +08:00
|
|
|
|
1997-05-06 06:15:02 +08:00
|
|
|
typedef struct {
|
|
|
|
getreadbufferproc bf_getreadbuffer;
|
|
|
|
getwritebufferproc bf_getwritebuffer;
|
|
|
|
getsegcountproc bf_getsegcount;
|
Changes by Greg Stein (code) and GvR (design).
Add a new member to the PyBufferProcs struct, bf_getcharbuffer. For
backward compatibility, this member should only be used (this includes
testing for NULL!) when the flag Py_TPFLAGS_HAVE_GETCHARBUFFER is set
in the type structure, below. Note that if its flag is not set, we
may be looking at an extension module compiled for 1.5.1, which will
have garbage at the bf_getcharbuffer member (because the struct wasn't
as long then). If the flag is one, the pointer may still be NULL.
The function found at this member is used in a similar manner as
bf_getreadbuffer, but it is known to point to 8-bit character data.
(See discussion in getargs.c checked in later.)
As a general feature for extending the type structure and the various
structures that (may) hang off it in a backwards compatible way, we
rename the tp_xxx4 "spare" slot to tp_flags. In 1.5.1 and before,
this slot was always zero. In 1.5.1, it may contain various flags
indicating extra fields that weren't present in 1.5.1. The only flag
defined so far is for the bf_getcharbuffer member of the PyBufferProcs
struct.
Note that the new spares (tp_xxx5 - tp_xxx8), once they become used,
should also be protected by a flag (or flags) in tp_flags.
1998-10-08 10:10:56 +08:00
|
|
|
getcharbufferproc bf_getcharbuffer;
|
1997-05-06 06:15:02 +08:00
|
|
|
} PyBufferProcs;
|
2002-07-07 13:13:56 +08:00
|
|
|
|
1997-05-06 06:15:02 +08:00
|
|
|
|
2002-04-12 09:57:06 +08:00
|
|
|
typedef void (*freefunc)(void *);
|
2000-07-08 08:32:04 +08:00
|
|
|
typedef void (*destructor)(PyObject *);
|
|
|
|
typedef int (*printfunc)(PyObject *, FILE *, int);
|
|
|
|
typedef PyObject *(*getattrfunc)(PyObject *, char *);
|
|
|
|
typedef PyObject *(*getattrofunc)(PyObject *, PyObject *);
|
|
|
|
typedef int (*setattrfunc)(PyObject *, char *, PyObject *);
|
|
|
|
typedef int (*setattrofunc)(PyObject *, PyObject *, PyObject *);
|
|
|
|
typedef int (*cmpfunc)(PyObject *, PyObject *);
|
|
|
|
typedef PyObject *(*reprfunc)(PyObject *);
|
|
|
|
typedef long (*hashfunc)(PyObject *);
|
2001-01-17 23:20:39 +08:00
|
|
|
typedef PyObject *(*richcmpfunc) (PyObject *, PyObject *, int);
|
2001-04-21 03:13:02 +08:00
|
|
|
typedef PyObject *(*getiterfunc) (PyObject *);
|
2001-04-23 22:08:49 +08:00
|
|
|
typedef PyObject *(*iternextfunc) (PyObject *);
|
2001-08-02 12:15:00 +08:00
|
|
|
typedef PyObject *(*descrgetfunc) (PyObject *, PyObject *, PyObject *);
|
|
|
|
typedef int (*descrsetfunc) (PyObject *, PyObject *, PyObject *);
|
|
|
|
typedef int (*initproc)(PyObject *, PyObject *, PyObject *);
|
|
|
|
typedef PyObject *(*newfunc)(struct _typeobject *, PyObject *, PyObject *);
|
|
|
|
typedef PyObject *(*allocfunc)(struct _typeobject *, int);
|
1994-08-01 19:34:53 +08:00
|
|
|
|
1990-10-14 20:07:46 +08:00
|
|
|
typedef struct _typeobject {
|
1995-01-12 19:45:45 +08:00
|
|
|
PyObject_VAR_HEAD
|
2001-12-09 02:02:58 +08:00
|
|
|
char *tp_name; /* For printing, in format "<module>.<name>" */
|
1995-01-05 03:06:22 +08:00
|
|
|
int tp_basicsize, tp_itemsize; /* For allocation */
|
2002-07-07 13:13:56 +08:00
|
|
|
|
1990-10-14 20:07:46 +08:00
|
|
|
/* Methods to implement standard operations */
|
2002-07-07 13:13:56 +08:00
|
|
|
|
1994-08-01 19:34:53 +08:00
|
|
|
destructor tp_dealloc;
|
|
|
|
printfunc tp_print;
|
|
|
|
getattrfunc tp_getattr;
|
|
|
|
setattrfunc tp_setattr;
|
|
|
|
cmpfunc tp_compare;
|
|
|
|
reprfunc tp_repr;
|
2002-07-07 13:13:56 +08:00
|
|
|
|
1990-10-14 20:07:46 +08:00
|
|
|
/* Method suites for standard classes */
|
2002-07-07 13:13:56 +08:00
|
|
|
|
1995-01-12 19:45:45 +08:00
|
|
|
PyNumberMethods *tp_as_number;
|
|
|
|
PySequenceMethods *tp_as_sequence;
|
|
|
|
PyMappingMethods *tp_as_mapping;
|
1993-03-29 18:43:31 +08:00
|
|
|
|
2000-03-22 00:14:47 +08:00
|
|
|
/* More standard operations (here for binary compatibility) */
|
1993-03-29 18:43:31 +08:00
|
|
|
|
1994-08-01 19:34:53 +08:00
|
|
|
hashfunc tp_hash;
|
1995-07-18 22:21:06 +08:00
|
|
|
ternaryfunc tp_call;
|
1995-01-07 18:32:04 +08:00
|
|
|
reprfunc tp_str;
|
1996-08-10 04:48:52 +08:00
|
|
|
getattrofunc tp_getattro;
|
|
|
|
setattrofunc tp_setattro;
|
1995-01-07 18:32:04 +08:00
|
|
|
|
1997-05-06 06:15:02 +08:00
|
|
|
/* Functions to access object as input/output buffer */
|
|
|
|
PyBufferProcs *tp_as_buffer;
|
2002-07-07 13:13:56 +08:00
|
|
|
|
Changes by Greg Stein (code) and GvR (design).
Add a new member to the PyBufferProcs struct, bf_getcharbuffer. For
backward compatibility, this member should only be used (this includes
testing for NULL!) when the flag Py_TPFLAGS_HAVE_GETCHARBUFFER is set
in the type structure, below. Note that if its flag is not set, we
may be looking at an extension module compiled for 1.5.1, which will
have garbage at the bf_getcharbuffer member (because the struct wasn't
as long then). If the flag is one, the pointer may still be NULL.
The function found at this member is used in a similar manner as
bf_getreadbuffer, but it is known to point to 8-bit character data.
(See discussion in getargs.c checked in later.)
As a general feature for extending the type structure and the various
structures that (may) hang off it in a backwards compatible way, we
rename the tp_xxx4 "spare" slot to tp_flags. In 1.5.1 and before,
this slot was always zero. In 1.5.1, it may contain various flags
indicating extra fields that weren't present in 1.5.1. The only flag
defined so far is for the bf_getcharbuffer member of the PyBufferProcs
struct.
Note that the new spares (tp_xxx5 - tp_xxx8), once they become used,
should also be protected by a flag (or flags) in tp_flags.
1998-10-08 10:10:56 +08:00
|
|
|
/* Flags to define presence of optional/expanded features */
|
|
|
|
long tp_flags;
|
1995-01-07 18:32:04 +08:00
|
|
|
|
|
|
|
char *tp_doc; /* Documentation string */
|
|
|
|
|
2001-08-16 02:32:33 +08:00
|
|
|
/* Assigned meaning in release 2.0 */
|
2000-06-23 22:18:11 +08:00
|
|
|
/* call function for all accessible objects */
|
|
|
|
traverseproc tp_traverse;
|
2002-07-07 13:13:56 +08:00
|
|
|
|
2000-06-23 22:18:11 +08:00
|
|
|
/* delete references to contained objects */
|
|
|
|
inquiry tp_clear;
|
|
|
|
|
2001-08-16 02:32:33 +08:00
|
|
|
/* Assigned meaning in release 2.1 */
|
2001-01-17 23:20:39 +08:00
|
|
|
/* rich comparisons */
|
|
|
|
richcmpfunc tp_richcompare;
|
|
|
|
|
2001-02-01 13:27:45 +08:00
|
|
|
/* weak reference enabler */
|
|
|
|
long tp_weaklistoffset;
|
1998-04-24 03:16:44 +08:00
|
|
|
|
2001-08-16 02:32:33 +08:00
|
|
|
/* Added in release 2.2 */
|
2001-04-21 03:13:02 +08:00
|
|
|
/* Iterators */
|
|
|
|
getiterfunc tp_iter;
|
2001-04-23 22:08:49 +08:00
|
|
|
iternextfunc tp_iternext;
|
2001-04-21 03:13:02 +08:00
|
|
|
|
2001-08-02 12:15:00 +08:00
|
|
|
/* Attribute descriptor and subclassing stuff */
|
|
|
|
struct PyMethodDef *tp_methods;
|
2001-09-21 04:46:19 +08:00
|
|
|
struct PyMemberDef *tp_members;
|
2001-09-21 05:45:26 +08:00
|
|
|
struct PyGetSetDef *tp_getset;
|
2001-08-02 12:15:00 +08:00
|
|
|
struct _typeobject *tp_base;
|
|
|
|
PyObject *tp_dict;
|
|
|
|
descrgetfunc tp_descr_get;
|
|
|
|
descrsetfunc tp_descr_set;
|
|
|
|
long tp_dictoffset;
|
|
|
|
initproc tp_init;
|
|
|
|
allocfunc tp_alloc;
|
|
|
|
newfunc tp_new;
|
2002-04-12 09:57:06 +08:00
|
|
|
freefunc tp_free; /* Low-level free-memory routine */
|
Add Garbage Collection support to new-style classes (not yet to their
instances).
Also added GC support to various auxiliary types: super, property,
descriptors, wrappers, dictproxy. (Only type objects have a tp_clear
field; the other types are.)
One change was necessary to the GC infrastructure. We have statically
allocated type objects that don't have a GC header (and can't easily
be given one) and heap-allocated type objects that do have a GC
header. Giving these different metatypes would be really ugly: I
tried, and I had to modify pickle.py, cPickle.c, copy.py, add a new
invent a new name for the new metatype and make it a built-in, change
affected tests... In short, a mess. So instead, we add a new type
slot tp_is_gc, which is a simple Boolean function that determines
whether a particular instance has GC headers or not. This slot is
only relevant for types that have the (new) GC flag bit set. If the
tp_is_gc slot is NULL (by far the most common case), all instances of
the type are deemed to have GC headers. This slot is called by the
PyObject_IS_GC() macro (which is only used twice, both times in
gcmodule.c).
I also changed the extern declarations for a bunch of GC-related
functions (_PyObject_GC_Del etc.): these always exist but objimpl.h
only declared them when WITH_CYCLE_GC was defined, but I needed to be
able to reference them without #ifdefs. (When WITH_CYCLE_GC is not
defined, they do the same as their non-GC counterparts anyway.)
2001-10-03 05:24:57 +08:00
|
|
|
inquiry tp_is_gc; /* For PyObject_IS_GC */
|
2001-08-02 12:15:00 +08:00
|
|
|
PyObject *tp_bases;
|
|
|
|
PyObject *tp_mro; /* method resolution order */
|
2001-10-16 06:03:32 +08:00
|
|
|
PyObject *tp_cache;
|
2001-10-08 23:18:27 +08:00
|
|
|
PyObject *tp_subclasses;
|
|
|
|
PyObject *tp_weaklist;
|
2002-08-09 04:55:20 +08:00
|
|
|
destructor tp_del;
|
2001-08-02 12:15:00 +08:00
|
|
|
|
1993-10-11 20:54:31 +08:00
|
|
|
#ifdef COUNT_ALLOCS
|
2001-04-21 03:13:02 +08:00
|
|
|
/* these must be last and never explicitly initialized */
|
2001-08-02 12:15:00 +08:00
|
|
|
int tp_allocs;
|
|
|
|
int tp_frees;
|
1993-10-11 20:54:31 +08:00
|
|
|
int tp_maxalloc;
|
|
|
|
struct _typeobject *tp_next;
|
|
|
|
#endif
|
1995-01-12 19:45:45 +08:00
|
|
|
} PyTypeObject;
|
1990-10-14 20:07:46 +08:00
|
|
|
|
|
|
|
|
2003-03-07 23:13:17 +08:00
|
|
|
/* The *real* layout of a type object when allocated on the heap */
|
|
|
|
typedef struct _heaptypeobject {
|
|
|
|
/* Note: there's a dependency on the order of these members
|
|
|
|
in slotptr() in typeobject.c . */
|
|
|
|
PyTypeObject type;
|
|
|
|
PyNumberMethods as_number;
|
|
|
|
PyMappingMethods as_mapping;
|
|
|
|
PySequenceMethods as_sequence; /* as_sequence comes after as_mapping,
|
|
|
|
so that the mapping wins when both
|
|
|
|
the mapping and the sequence define
|
|
|
|
a given operator (e.g. __getitem__).
|
|
|
|
see add_operators() in typeobject.c . */
|
|
|
|
PyBufferProcs as_buffer;
|
|
|
|
PyObject *name, *slots;
|
|
|
|
/* here are optional user slots, followed by the members. */
|
|
|
|
} PyHeapTypeObject;
|
|
|
|
|
|
|
|
/* access macro to the members which are floating "behind" the object */
|
|
|
|
#define PyHeapType_GET_MEMBERS(etype) \
|
|
|
|
((PyMemberDef *)(((char *)etype) + (etype)->type.ob_type->tp_basicsize))
|
|
|
|
|
|
|
|
|
2001-08-02 12:15:00 +08:00
|
|
|
/* Generic type check */
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(int) PyType_IsSubtype(PyTypeObject *, PyTypeObject *);
|
2001-08-02 12:15:00 +08:00
|
|
|
#define PyObject_TypeCheck(ob, tp) \
|
|
|
|
((ob)->ob_type == (tp) || PyType_IsSubtype((ob)->ob_type, (tp)))
|
|
|
|
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_DATA(PyTypeObject) PyType_Type; /* built-in 'type' */
|
|
|
|
PyAPI_DATA(PyTypeObject) PyBaseObject_Type; /* built-in 'object' */
|
|
|
|
PyAPI_DATA(PyTypeObject) PySuper_Type; /* built-in 'super' */
|
2001-08-02 12:15:00 +08:00
|
|
|
|
|
|
|
#define PyType_Check(op) PyObject_TypeCheck(op, &PyType_Type)
|
2001-10-28 03:37:48 +08:00
|
|
|
#define PyType_CheckExact(op) ((op)->ob_type == &PyType_Type)
|
2001-08-02 12:15:00 +08:00
|
|
|
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(int) PyType_Ready(PyTypeObject *);
|
|
|
|
PyAPI_FUNC(PyObject *) PyType_GenericAlloc(PyTypeObject *, int);
|
|
|
|
PyAPI_FUNC(PyObject *) PyType_GenericNew(PyTypeObject *,
|
2001-08-02 12:15:00 +08:00
|
|
|
PyObject *, PyObject *);
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(PyObject *) _PyType_Lookup(PyTypeObject *, PyObject *);
|
1990-10-14 20:07:46 +08:00
|
|
|
|
1990-12-20 23:06:42 +08:00
|
|
|
/* Generic operations on objects */
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(int) PyObject_Print(PyObject *, FILE *, int);
|
|
|
|
PyAPI_FUNC(void) _PyObject_Dump(PyObject *);
|
|
|
|
PyAPI_FUNC(PyObject *) PyObject_Repr(PyObject *);
|
|
|
|
PyAPI_FUNC(PyObject *) PyObject_Str(PyObject *);
|
2001-08-18 02:39:25 +08:00
|
|
|
#ifdef Py_USING_UNICODE
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(PyObject *) PyObject_Unicode(PyObject *);
|
2001-08-18 02:39:25 +08:00
|
|
|
#endif
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(int) PyObject_Compare(PyObject *, PyObject *);
|
|
|
|
PyAPI_FUNC(PyObject *) PyObject_RichCompare(PyObject *, PyObject *, int);
|
|
|
|
PyAPI_FUNC(int) PyObject_RichCompareBool(PyObject *, PyObject *, int);
|
|
|
|
PyAPI_FUNC(PyObject *) PyObject_GetAttrString(PyObject *, char *);
|
|
|
|
PyAPI_FUNC(int) PyObject_SetAttrString(PyObject *, char *, PyObject *);
|
|
|
|
PyAPI_FUNC(int) PyObject_HasAttrString(PyObject *, char *);
|
|
|
|
PyAPI_FUNC(PyObject *) PyObject_GetAttr(PyObject *, PyObject *);
|
|
|
|
PyAPI_FUNC(int) PyObject_SetAttr(PyObject *, PyObject *, PyObject *);
|
|
|
|
PyAPI_FUNC(int) PyObject_HasAttr(PyObject *, PyObject *);
|
|
|
|
PyAPI_FUNC(PyObject **) _PyObject_GetDictPtr(PyObject *);
|
2003-03-18 03:46:11 +08:00
|
|
|
PyAPI_FUNC(PyObject *) PyObject_SelfIter(PyObject *);
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(PyObject *) PyObject_GenericGetAttr(PyObject *, PyObject *);
|
|
|
|
PyAPI_FUNC(int) PyObject_GenericSetAttr(PyObject *,
|
2001-08-02 12:15:00 +08:00
|
|
|
PyObject *, PyObject *);
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(long) PyObject_Hash(PyObject *);
|
|
|
|
PyAPI_FUNC(int) PyObject_IsTrue(PyObject *);
|
|
|
|
PyAPI_FUNC(int) PyObject_Not(PyObject *);
|
|
|
|
PyAPI_FUNC(int) PyCallable_Check(PyObject *);
|
|
|
|
PyAPI_FUNC(int) PyNumber_Coerce(PyObject **, PyObject **);
|
|
|
|
PyAPI_FUNC(int) PyNumber_CoerceEx(PyObject **, PyObject **);
|
1990-10-14 20:07:46 +08:00
|
|
|
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(void) PyObject_ClearWeakRefs(PyObject *);
|
2001-02-01 13:27:45 +08:00
|
|
|
|
2001-09-19 04:38:53 +08:00
|
|
|
/* A slot function whose address we need to compare */
|
|
|
|
extern int _PyObject_SlotCompare(PyObject *, PyObject *);
|
|
|
|
|
|
|
|
|
2001-09-05 06:08:56 +08:00
|
|
|
/* PyObject_Dir(obj) acts like Python __builtin__.dir(obj), returning a
|
|
|
|
list of strings. PyObject_Dir(NULL) is like __builtin__.dir(),
|
|
|
|
returning the names of the current locals. In this case, if there are
|
|
|
|
no current locals, NULL is returned, and PyErr_Occurred() is false.
|
|
|
|
*/
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(PyObject *) PyObject_Dir(PyObject *);
|
2001-09-05 06:08:56 +08:00
|
|
|
|
|
|
|
|
1998-04-11 06:32:24 +08:00
|
|
|
/* Helpers for printing recursive container types */
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(int) Py_ReprEnter(PyObject *);
|
|
|
|
PyAPI_FUNC(void) Py_ReprLeave(PyObject *);
|
1998-04-11 06:32:24 +08:00
|
|
|
|
2000-06-30 03:17:04 +08:00
|
|
|
/* Helpers for hash functions */
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(long) _Py_HashDouble(double);
|
|
|
|
PyAPI_FUNC(long) _Py_HashPointer(void*);
|
2000-06-30 03:17:04 +08:00
|
|
|
|
2001-02-02 04:20:45 +08:00
|
|
|
/* Helper for passing objects to printf and the like */
|
|
|
|
#define PyObject_REPR(obj) PyString_AS_STRING(PyObject_Repr(obj))
|
|
|
|
|
1990-10-14 20:07:46 +08:00
|
|
|
/* Flag bits for printing: */
|
1995-01-12 19:45:45 +08:00
|
|
|
#define Py_PRINT_RAW 1 /* No string quotes etc. */
|
1990-10-14 20:07:46 +08:00
|
|
|
|
Changes by Greg Stein (code) and GvR (design).
Add a new member to the PyBufferProcs struct, bf_getcharbuffer. For
backward compatibility, this member should only be used (this includes
testing for NULL!) when the flag Py_TPFLAGS_HAVE_GETCHARBUFFER is set
in the type structure, below. Note that if its flag is not set, we
may be looking at an extension module compiled for 1.5.1, which will
have garbage at the bf_getcharbuffer member (because the struct wasn't
as long then). If the flag is one, the pointer may still be NULL.
The function found at this member is used in a similar manner as
bf_getreadbuffer, but it is known to point to 8-bit character data.
(See discussion in getargs.c checked in later.)
As a general feature for extending the type structure and the various
structures that (may) hang off it in a backwards compatible way, we
rename the tp_xxx4 "spare" slot to tp_flags. In 1.5.1 and before,
this slot was always zero. In 1.5.1, it may contain various flags
indicating extra fields that weren't present in 1.5.1. The only flag
defined so far is for the bf_getcharbuffer member of the PyBufferProcs
struct.
Note that the new spares (tp_xxx5 - tp_xxx8), once they become used,
should also be protected by a flag (or flags) in tp_flags.
1998-10-08 10:10:56 +08:00
|
|
|
/*
|
2002-07-08 03:59:50 +08:00
|
|
|
`Type flags (tp_flags)
|
Changes by Greg Stein (code) and GvR (design).
Add a new member to the PyBufferProcs struct, bf_getcharbuffer. For
backward compatibility, this member should only be used (this includes
testing for NULL!) when the flag Py_TPFLAGS_HAVE_GETCHARBUFFER is set
in the type structure, below. Note that if its flag is not set, we
may be looking at an extension module compiled for 1.5.1, which will
have garbage at the bf_getcharbuffer member (because the struct wasn't
as long then). If the flag is one, the pointer may still be NULL.
The function found at this member is used in a similar manner as
bf_getreadbuffer, but it is known to point to 8-bit character data.
(See discussion in getargs.c checked in later.)
As a general feature for extending the type structure and the various
structures that (may) hang off it in a backwards compatible way, we
rename the tp_xxx4 "spare" slot to tp_flags. In 1.5.1 and before,
this slot was always zero. In 1.5.1, it may contain various flags
indicating extra fields that weren't present in 1.5.1. The only flag
defined so far is for the bf_getcharbuffer member of the PyBufferProcs
struct.
Note that the new spares (tp_xxx5 - tp_xxx8), once they become used,
should also be protected by a flag (or flags) in tp_flags.
1998-10-08 10:10:56 +08:00
|
|
|
|
|
|
|
These flags are used to extend the type structure in a backwards-compatible
|
|
|
|
fashion. Extensions can use the flags to indicate (and test) when a given
|
|
|
|
type structure contains a new feature. The Python core will use these when
|
|
|
|
introducing new functionality between major revisions (to avoid mid-version
|
|
|
|
changes in the PYTHON_API_VERSION).
|
|
|
|
|
|
|
|
Arbitration of the flag bit positions will need to be coordinated among
|
|
|
|
all extension writers who publically release their extensions (this will
|
|
|
|
be fewer than you might expect!)..
|
|
|
|
|
|
|
|
Python 1.5.2 introduced the bf_getcharbuffer slot into PyBufferProcs.
|
|
|
|
|
|
|
|
Type definitions should use Py_TPFLAGS_DEFAULT for their tp_flags value.
|
|
|
|
|
|
|
|
Code can use PyType_HasFeature(type_ob, flag_value) to test whether the
|
|
|
|
given type object has a specified feature.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/* PyBufferProcs contains bf_getcharbuffer */
|
|
|
|
#define Py_TPFLAGS_HAVE_GETCHARBUFFER (1L<<0)
|
|
|
|
|
2000-02-28 23:00:40 +08:00
|
|
|
/* PySequenceMethods contains sq_contains */
|
|
|
|
#define Py_TPFLAGS_HAVE_SEQUENCE_IN (1L<<1)
|
|
|
|
|
2001-08-30 07:46:35 +08:00
|
|
|
/* This is here for backwards compatibility. Extensions that use the old GC
|
|
|
|
* API will still compile but the objects will not be tracked by the GC. */
|
|
|
|
#define Py_TPFLAGS_GC 0 /* used to be (1L<<2) */
|
2000-06-24 03:37:02 +08:00
|
|
|
|
2000-08-25 04:09:45 +08:00
|
|
|
/* PySequenceMethods and PyNumberMethods contain in-place operators */
|
|
|
|
#define Py_TPFLAGS_HAVE_INPLACEOPS (1L<<3)
|
|
|
|
|
2001-01-04 09:31:50 +08:00
|
|
|
/* PyNumberMethods do their own coercion */
|
2001-01-17 23:20:39 +08:00
|
|
|
#define Py_TPFLAGS_CHECKTYPES (1L<<4)
|
2001-01-04 09:31:50 +08:00
|
|
|
|
2001-04-21 03:13:02 +08:00
|
|
|
/* tp_richcompare is defined */
|
2001-01-25 06:13:48 +08:00
|
|
|
#define Py_TPFLAGS_HAVE_RICHCOMPARE (1L<<5)
|
|
|
|
|
2001-02-03 02:17:30 +08:00
|
|
|
/* Objects which are weakly referencable if their tp_weaklistoffset is >0 */
|
|
|
|
#define Py_TPFLAGS_HAVE_WEAKREFS (1L<<6)
|
|
|
|
|
2001-04-21 03:13:02 +08:00
|
|
|
/* tp_iter is defined */
|
|
|
|
#define Py_TPFLAGS_HAVE_ITER (1L<<7)
|
|
|
|
|
2001-08-08 13:00:18 +08:00
|
|
|
/* New members introduced by Python 2.2 exist */
|
2001-08-02 12:15:00 +08:00
|
|
|
#define Py_TPFLAGS_HAVE_CLASS (1L<<8)
|
|
|
|
|
|
|
|
/* Set if the type object is dynamically allocated */
|
|
|
|
#define Py_TPFLAGS_HEAPTYPE (1L<<9)
|
|
|
|
|
|
|
|
/* Set if the type allows subclassing */
|
|
|
|
#define Py_TPFLAGS_BASETYPE (1L<<10)
|
|
|
|
|
2001-08-11 01:37:02 +08:00
|
|
|
/* Set if the type is 'ready' -- fully initialized */
|
|
|
|
#define Py_TPFLAGS_READY (1L<<12)
|
|
|
|
|
|
|
|
/* Set while the type is being 'readied', to prevent recursive ready calls */
|
|
|
|
#define Py_TPFLAGS_READYING (1L<<13)
|
|
|
|
|
2001-08-30 07:46:35 +08:00
|
|
|
/* Objects support garbage collection (see objimp.h) */
|
|
|
|
#define Py_TPFLAGS_HAVE_GC (1L<<14)
|
|
|
|
|
2001-01-25 06:13:48 +08:00
|
|
|
#define Py_TPFLAGS_DEFAULT ( \
|
|
|
|
Py_TPFLAGS_HAVE_GETCHARBUFFER | \
|
2000-08-25 04:09:45 +08:00
|
|
|
Py_TPFLAGS_HAVE_SEQUENCE_IN | \
|
2001-01-25 06:13:48 +08:00
|
|
|
Py_TPFLAGS_HAVE_INPLACEOPS | \
|
|
|
|
Py_TPFLAGS_HAVE_RICHCOMPARE | \
|
2001-02-03 02:17:30 +08:00
|
|
|
Py_TPFLAGS_HAVE_WEAKREFS | \
|
2001-04-21 03:13:02 +08:00
|
|
|
Py_TPFLAGS_HAVE_ITER | \
|
2001-08-02 12:15:00 +08:00
|
|
|
Py_TPFLAGS_HAVE_CLASS | \
|
2001-01-25 06:13:48 +08:00
|
|
|
0)
|
Changes by Greg Stein (code) and GvR (design).
Add a new member to the PyBufferProcs struct, bf_getcharbuffer. For
backward compatibility, this member should only be used (this includes
testing for NULL!) when the flag Py_TPFLAGS_HAVE_GETCHARBUFFER is set
in the type structure, below. Note that if its flag is not set, we
may be looking at an extension module compiled for 1.5.1, which will
have garbage at the bf_getcharbuffer member (because the struct wasn't
as long then). If the flag is one, the pointer may still be NULL.
The function found at this member is used in a similar manner as
bf_getreadbuffer, but it is known to point to 8-bit character data.
(See discussion in getargs.c checked in later.)
As a general feature for extending the type structure and the various
structures that (may) hang off it in a backwards compatible way, we
rename the tp_xxx4 "spare" slot to tp_flags. In 1.5.1 and before,
this slot was always zero. In 1.5.1, it may contain various flags
indicating extra fields that weren't present in 1.5.1. The only flag
defined so far is for the bf_getcharbuffer member of the PyBufferProcs
struct.
Note that the new spares (tp_xxx5 - tp_xxx8), once they become used,
should also be protected by a flag (or flags) in tp_flags.
1998-10-08 10:10:56 +08:00
|
|
|
|
|
|
|
#define PyType_HasFeature(t,f) (((t)->tp_flags & (f)) != 0)
|
|
|
|
|
|
|
|
|
1990-10-14 20:07:46 +08:00
|
|
|
/*
|
1995-01-12 19:45:45 +08:00
|
|
|
The macros Py_INCREF(op) and Py_DECREF(op) are used to increment or decrement
|
2002-07-08 03:59:50 +08:00
|
|
|
reference counts. Py_DECREF calls the object's deallocator function when
|
|
|
|
the refcount falls to 0; for
|
1990-10-14 20:07:46 +08:00
|
|
|
objects that don't contain references to other objects or heap memory
|
|
|
|
this can be the standard function free(). Both macros can be used
|
2002-07-08 03:59:50 +08:00
|
|
|
wherever a void expression is allowed. The argument must not be a
|
|
|
|
NIL pointer. If it may be NIL, use Py_XINCREF/Py_XDECREF instead.
|
|
|
|
The macro _Py_NewReference(op) initialize reference counts to 1, and
|
|
|
|
in special builds (Py_REF_DEBUG, Py_TRACE_REFS) performs additional
|
|
|
|
bookkeeping appropriate to the special build.
|
1990-10-14 20:07:46 +08:00
|
|
|
|
|
|
|
We assume that the reference count field can never overflow; this can
|
2002-07-08 03:59:50 +08:00
|
|
|
be proven when the size of the field is the same as the pointer size, so
|
|
|
|
we ignore the possibility. Provided a C int is at least 32 bits (which
|
|
|
|
is implicitly assumed in many parts of this code), that's enough for
|
|
|
|
about 2**31 references to an object.
|
|
|
|
|
|
|
|
XXX The following became out of date in Python 2.2, but I'm not sure
|
|
|
|
XXX what the full truth is now. Certainly, heap-allocated type objects
|
|
|
|
XXX can and should be deallocated.
|
1990-10-14 20:07:46 +08:00
|
|
|
Type objects should never be deallocated; the type pointer in an object
|
|
|
|
is not considered to be a reference to the type object, to save
|
|
|
|
complications in the deallocation function. (This is actually a
|
|
|
|
decision that's up to the implementer of each new type so if you want,
|
|
|
|
you can count such references to the type object.)
|
|
|
|
|
1995-01-12 19:45:45 +08:00
|
|
|
*** WARNING*** The Py_DECREF macro must have a side-effect-free argument
|
1990-10-14 20:07:46 +08:00
|
|
|
since it may evaluate its argument multiple times. (The alternative
|
|
|
|
would be to mace it a proper function or assign it to a global temporary
|
|
|
|
variable first, both of which are slower; and in a multi-threaded
|
|
|
|
environment the global variable trick is not safe.)
|
|
|
|
*/
|
|
|
|
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
/* First define a pile of simple helper macros, one set per special
|
|
|
|
* build symbol. These either expand to the obvious things, or to
|
|
|
|
* nothing at all when the special mode isn't in effect. The main
|
|
|
|
* macros can later be defined just once then, yet expand to different
|
|
|
|
* things depending on which special build options are and aren't in effect.
|
|
|
|
* Trust me <wink>: while painful, this is 20x easier to understand than,
|
|
|
|
* e.g, defining _Py_NewReference five different times in a maze of nested
|
|
|
|
* #ifdefs (we used to do that -- it was impenetrable).
|
|
|
|
*/
|
2002-07-08 03:59:50 +08:00
|
|
|
#ifdef Py_REF_DEBUG
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_DATA(long) _Py_RefTotal;
|
|
|
|
PyAPI_FUNC(void) _Py_NegativeRefcount(const char *fname,
|
2002-07-09 10:57:01 +08:00
|
|
|
int lineno, PyObject *op);
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
#define _Py_INC_REFTOTAL _Py_RefTotal++
|
|
|
|
#define _Py_DEC_REFTOTAL _Py_RefTotal--
|
|
|
|
#define _Py_REF_DEBUG_COMMA ,
|
|
|
|
#define _Py_CHECK_REFCNT(OP) \
|
2002-07-09 10:57:01 +08:00
|
|
|
{ if ((OP)->ob_refcnt < 0) \
|
|
|
|
_Py_NegativeRefcount(__FILE__, __LINE__, \
|
|
|
|
(PyObject *)(OP)); \
|
|
|
|
}
|
2002-07-08 03:59:50 +08:00
|
|
|
#else
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
#define _Py_INC_REFTOTAL
|
|
|
|
#define _Py_DEC_REFTOTAL
|
|
|
|
#define _Py_REF_DEBUG_COMMA
|
|
|
|
#define _Py_CHECK_REFCNT(OP) /* a semicolon */;
|
2002-07-10 14:34:15 +08:00
|
|
|
#endif /* Py_REF_DEBUG */
|
2002-07-08 03:59:50 +08:00
|
|
|
|
|
|
|
#ifdef COUNT_ALLOCS
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(void) inc_count(PyTypeObject *);
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
#define _Py_INC_TPALLOCS(OP) inc_count((OP)->ob_type)
|
|
|
|
#define _Py_INC_TPFREES(OP) (OP)->ob_type->tp_frees++
|
|
|
|
#define _Py_DEC_TPFREES(OP) (OP)->ob_type->tp_frees--
|
|
|
|
#define _Py_COUNT_ALLOCS_COMMA ,
|
2002-07-08 03:59:50 +08:00
|
|
|
#else
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
#define _Py_INC_TPALLOCS(OP)
|
|
|
|
#define _Py_INC_TPFREES(OP)
|
|
|
|
#define _Py_DEC_TPFREES(OP)
|
|
|
|
#define _Py_COUNT_ALLOCS_COMMA
|
2002-07-10 14:34:15 +08:00
|
|
|
#endif /* COUNT_ALLOCS */
|
1990-10-14 20:07:46 +08:00
|
|
|
|
1996-08-13 05:31:32 +08:00
|
|
|
#ifdef Py_TRACE_REFS
|
2002-07-08 03:59:50 +08:00
|
|
|
/* Py_TRACE_REFS is such major surgery that we call external routines. */
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(void) _Py_NewReference(PyObject *);
|
|
|
|
PyAPI_FUNC(void) _Py_ForgetReference(PyObject *);
|
|
|
|
PyAPI_FUNC(void) _Py_Dealloc(PyObject *);
|
|
|
|
PyAPI_FUNC(void) _Py_PrintReferences(FILE *);
|
2003-03-24 01:52:28 +08:00
|
|
|
PyAPI_FUNC(void) _Py_AddToAllObjects(PyObject *, int force);
|
1990-10-14 20:07:46 +08:00
|
|
|
|
2002-07-08 03:59:50 +08:00
|
|
|
#else
|
|
|
|
/* Without Py_TRACE_REFS, there's little enough to do that we expand code
|
|
|
|
* inline.
|
|
|
|
*/
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
#define _Py_NewReference(op) ( \
|
|
|
|
_Py_INC_TPALLOCS(op) _Py_COUNT_ALLOCS_COMMA \
|
|
|
|
_Py_INC_REFTOTAL _Py_REF_DEBUG_COMMA \
|
2002-07-08 03:59:50 +08:00
|
|
|
(op)->ob_refcnt = 1)
|
1993-10-11 20:54:31 +08:00
|
|
|
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
#define _Py_ForgetReference(op) _Py_INC_TPFREES(op)
|
1996-05-23 00:33:22 +08:00
|
|
|
|
2002-07-10 14:34:15 +08:00
|
|
|
#define _Py_Dealloc(op) ( \
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
_Py_INC_TPFREES(op) _Py_COUNT_ALLOCS_COMMA \
|
2002-07-08 03:59:50 +08:00
|
|
|
(*(op)->ob_type->tp_dealloc)((PyObject *)(op)))
|
1996-05-23 00:33:22 +08:00
|
|
|
#endif /* !Py_TRACE_REFS */
|
|
|
|
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
#define Py_INCREF(op) ( \
|
|
|
|
_Py_INC_REFTOTAL _Py_REF_DEBUG_COMMA \
|
2002-07-08 03:59:50 +08:00
|
|
|
(op)->ob_refcnt++)
|
|
|
|
|
object.h special-build macro minefield: renamed all the new lexical
helper macros to something saner, and used them appropriately in other
files too, to reduce #ifdef blocks.
classobject.c, instance_dealloc(): One of my worst Python Memories is
trying to fix this routine a few years ago when COUNT_ALLOCS was defined
but Py_TRACE_REFS wasn't. The special-build code here is way too
complicated. Now it's much simpler. Difference: in a Py_TRACE_REFS
build, the instance is no longer in the doubly-linked list of live
objects while its __del__ method is executing, and that may be visible
via sys.getobjects() called from a __del__ method. Tough -- the object
is presumed dead while its __del__ is executing anyway, and not calling
_Py_NewReference() at the start allows enormous code simplification.
typeobject.c, call_finalizer(): The special-build instance_dealloc()
pain apparently spread to here too via cut-'n-paste, and this is much
simpler now too. In addition, I didn't understand why this routine
was calling _PyObject_GC_TRACK() after a resurrection, since there's no
plausible way _PyObject_GC_UNTRACK() could have been called on the
object by this point. I suspect it was left over from pasting the
instance_delloc() code. Instead asserted that the object is still
tracked. Caution: I suspect we don't have a test that actually
exercises the subtype_dealloc() __del__-resurrected-me code.
2002-07-11 14:23:50 +08:00
|
|
|
#define Py_DECREF(op) \
|
|
|
|
if (_Py_DEC_REFTOTAL _Py_REF_DEBUG_COMMA \
|
|
|
|
--(op)->ob_refcnt != 0) \
|
|
|
|
_Py_CHECK_REFCNT(op) \
|
|
|
|
else \
|
1997-08-05 10:30:44 +08:00
|
|
|
_Py_Dealloc((PyObject *)(op))
|
1990-10-14 20:07:46 +08:00
|
|
|
|
1990-12-20 23:06:42 +08:00
|
|
|
/* Macros to use in case the object pointer may be NULL: */
|
1995-01-12 19:45:45 +08:00
|
|
|
#define Py_XINCREF(op) if ((op) == NULL) ; else Py_INCREF(op)
|
|
|
|
#define Py_XDECREF(op) if ((op) == NULL) ; else Py_DECREF(op)
|
1990-10-14 20:07:46 +08:00
|
|
|
|
|
|
|
/*
|
1995-01-12 19:45:45 +08:00
|
|
|
_Py_NoneStruct is an object of undefined type which can be used in contexts
|
1990-10-14 20:07:46 +08:00
|
|
|
where NULL (nil) is not suitable (since NULL often means 'error').
|
|
|
|
|
1995-01-12 19:45:45 +08:00
|
|
|
Don't forget to apply Py_INCREF() when returning this value!!!
|
1990-10-14 20:07:46 +08:00
|
|
|
*/
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_DATA(PyObject) _Py_NoneStruct; /* Don't use this directly */
|
1995-01-12 19:45:45 +08:00
|
|
|
#define Py_None (&_Py_NoneStruct)
|
1990-10-14 20:07:46 +08:00
|
|
|
|
2001-01-04 09:31:50 +08:00
|
|
|
/*
|
|
|
|
Py_NotImplemented is a singleton used to signal that an operation is
|
|
|
|
not implemented for a given type combination.
|
|
|
|
*/
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_DATA(PyObject) _Py_NotImplementedStruct; /* Don't use this directly */
|
2001-01-04 09:31:50 +08:00
|
|
|
#define Py_NotImplemented (&_Py_NotImplementedStruct)
|
1990-10-14 20:07:46 +08:00
|
|
|
|
2001-01-17 23:20:39 +08:00
|
|
|
/* Rich comparison opcodes */
|
|
|
|
#define Py_LT 0
|
|
|
|
#define Py_LE 1
|
|
|
|
#define Py_EQ 2
|
|
|
|
#define Py_NE 3
|
|
|
|
#define Py_GT 4
|
|
|
|
#define Py_GE 5
|
|
|
|
|
1994-08-01 19:34:53 +08:00
|
|
|
/*
|
2002-07-18 00:30:39 +08:00
|
|
|
Define staticforward and statichere for source compatibility with old
|
|
|
|
C extensions.
|
|
|
|
|
|
|
|
The staticforward define was needed to support certain broken C
|
|
|
|
compilers (notably SCO ODT 3.0, perhaps early AIX as well) botched the
|
|
|
|
static keyword when it was used with a forward declaration of a static
|
|
|
|
initialized structure. Standard C allows the forward declaration with
|
|
|
|
static, and we've decided to stop catering to broken C compilers.
|
|
|
|
(In fact, we expect that the compilers are all fixed eight years later.)
|
1994-08-01 19:34:53 +08:00
|
|
|
*/
|
|
|
|
|
|
|
|
#define staticforward static
|
1995-02-22 05:06:10 +08:00
|
|
|
#define statichere static
|
1994-08-01 19:34:53 +08:00
|
|
|
|
|
|
|
|
1990-10-14 20:07:46 +08:00
|
|
|
/*
|
|
|
|
More conventions
|
|
|
|
================
|
|
|
|
|
|
|
|
Argument Checking
|
|
|
|
-----------------
|
|
|
|
|
|
|
|
Functions that take objects as arguments normally don't check for nil
|
|
|
|
arguments, but they do check the type of the argument, and return an
|
|
|
|
error if the function doesn't apply to the type.
|
|
|
|
|
|
|
|
Failure Modes
|
|
|
|
-------------
|
|
|
|
|
|
|
|
Functions may fail for a variety of reasons, including running out of
|
1990-12-20 23:06:42 +08:00
|
|
|
memory. This is communicated to the caller in two ways: an error string
|
|
|
|
is set (see errors.h), and the function result differs: functions that
|
|
|
|
normally return a pointer return NULL for failure, functions returning
|
|
|
|
an integer return -1 (which could be a legal return value too!), and
|
|
|
|
other functions return 0 for success and -1 for failure.
|
2002-07-08 03:59:50 +08:00
|
|
|
Callers should always check for errors before using the result. If
|
|
|
|
an error was set, the caller must either explicitly clear it, or pass
|
|
|
|
the error on to its caller.
|
1990-10-14 20:07:46 +08:00
|
|
|
|
|
|
|
Reference Counts
|
|
|
|
----------------
|
|
|
|
|
|
|
|
It takes a while to get used to the proper usage of reference counts.
|
|
|
|
|
|
|
|
Functions that create an object set the reference count to 1; such new
|
1995-01-12 19:45:45 +08:00
|
|
|
objects must be stored somewhere or destroyed again with Py_DECREF().
|
|
|
|
Functions that 'store' objects such as PyTuple_SetItem() and
|
|
|
|
PyDict_SetItemString()
|
1990-10-14 20:07:46 +08:00
|
|
|
don't increment the reference count of the object, since the most
|
|
|
|
frequent use is to store a fresh object. Functions that 'retrieve'
|
1995-01-12 19:45:45 +08:00
|
|
|
objects such as PyTuple_GetItem() and PyDict_GetItemString() also
|
|
|
|
don't increment
|
1990-10-14 20:07:46 +08:00
|
|
|
the reference count, since most frequently the object is only looked at
|
|
|
|
quickly. Thus, to retrieve an object and store it again, the caller
|
1995-01-12 19:45:45 +08:00
|
|
|
must call Py_INCREF() explicitly.
|
1990-10-14 20:07:46 +08:00
|
|
|
|
1995-01-12 19:45:45 +08:00
|
|
|
NOTE: functions that 'consume' a reference count like
|
1997-09-06 01:53:53 +08:00
|
|
|
PyList_SetItemString() even consume the reference if the object wasn't
|
|
|
|
stored, to simplify error handling.
|
1990-10-14 20:07:46 +08:00
|
|
|
|
|
|
|
It seems attractive to make other functions that take an object as
|
|
|
|
argument consume a reference count; however this may quickly get
|
|
|
|
confusing (even the current practice is already confusing). Consider
|
1995-01-12 19:45:45 +08:00
|
|
|
it carefully, it may save lots of calls to Py_INCREF() and Py_DECREF() at
|
1990-10-14 20:07:46 +08:00
|
|
|
times.
|
|
|
|
*/
|
1993-07-28 17:05:47 +08:00
|
|
|
|
2000-03-14 00:01:29 +08:00
|
|
|
|
2002-07-07 13:13:56 +08:00
|
|
|
/* Trashcan mechanism, thanks to Christian Tismer.
|
2000-03-14 00:01:29 +08:00
|
|
|
|
2002-07-07 13:13:56 +08:00
|
|
|
When deallocating a container object, it's possible to trigger an unbounded
|
|
|
|
chain of deallocations, as each Py_DECREF in turn drops the refcount on "the
|
|
|
|
next" object in the chain to 0. This can easily lead to stack faults, and
|
|
|
|
especially in threads (which typically have less stack space to work with).
|
2000-03-14 00:01:29 +08:00
|
|
|
|
2002-07-07 13:13:56 +08:00
|
|
|
A container object that participates in cyclic gc can avoid this by
|
|
|
|
bracketing the body of its tp_dealloc function with a pair of macros:
|
|
|
|
|
|
|
|
static void
|
|
|
|
mytype_dealloc(mytype *p)
|
|
|
|
{
|
|
|
|
... declarations go here ...
|
|
|
|
|
|
|
|
PyObject_GC_UnTrack(p); // must untrack first
|
|
|
|
Py_TRASHCAN_SAFE_BEGIN(p)
|
|
|
|
... The body of the deallocator goes here, including all calls ...
|
|
|
|
... to Py_DECREF on contained objects. ...
|
|
|
|
Py_TRASHCAN_SAFE_END(p)
|
|
|
|
}
|
|
|
|
|
2002-08-08 04:53:05 +08:00
|
|
|
CAUTION: Never return from the middle of the body! If the body needs to
|
|
|
|
"get out early", put a label immediately before the Py_TRASHCAN_SAFE_END
|
|
|
|
call, and goto it. Else the call-depth counter (see below) will stay
|
|
|
|
above 0 forever, and the trashcan will never get emptied.
|
|
|
|
|
2002-07-07 13:13:56 +08:00
|
|
|
How it works: The BEGIN macro increments a call-depth counter. So long
|
|
|
|
as this counter is small, the body of the deallocator is run directly without
|
|
|
|
further ado. But if the counter gets large, it instead adds p to a list of
|
|
|
|
objects to be deallocated later, skips the body of the deallocator, and
|
|
|
|
resumes execution after the END macro. The tp_dealloc routine then returns
|
|
|
|
without deallocating anything (and so unbounded call-stack depth is avoided).
|
|
|
|
|
|
|
|
When the call stack finishes unwinding again, code generated by the END macro
|
|
|
|
notices this, and calls another routine to deallocate all the objects that
|
|
|
|
may have been added to the list of deferred deallocations. In effect, a
|
|
|
|
chain of N deallocations is broken into N / PyTrash_UNWIND_LEVEL pieces,
|
|
|
|
with the call stack never exceeding a depth of PyTrash_UNWIND_LEVEL.
|
|
|
|
*/
|
2000-03-14 00:01:29 +08:00
|
|
|
|
2002-07-29 21:42:14 +08:00
|
|
|
PyAPI_FUNC(void) _PyTrash_deposit_object(PyObject*);
|
|
|
|
PyAPI_FUNC(void) _PyTrash_destroy_chain(void);
|
|
|
|
PyAPI_DATA(int) _PyTrash_delete_nesting;
|
|
|
|
PyAPI_DATA(PyObject *) _PyTrash_delete_later;
|
2000-03-14 00:01:29 +08:00
|
|
|
|
2002-07-07 13:13:56 +08:00
|
|
|
#define PyTrash_UNWIND_LEVEL 50
|
2000-03-14 00:01:29 +08:00
|
|
|
|
2002-07-07 13:13:56 +08:00
|
|
|
#define Py_TRASHCAN_SAFE_BEGIN(op) \
|
|
|
|
if (_PyTrash_delete_nesting < PyTrash_UNWIND_LEVEL) { \
|
|
|
|
++_PyTrash_delete_nesting;
|
|
|
|
/* The body of the deallocator is here. */
|
|
|
|
#define Py_TRASHCAN_SAFE_END(op) \
|
|
|
|
--_PyTrash_delete_nesting; \
|
|
|
|
if (_PyTrash_delete_later && _PyTrash_delete_nesting <= 0) \
|
|
|
|
_PyTrash_destroy_chain(); \
|
|
|
|
} \
|
|
|
|
else \
|
|
|
|
_PyTrash_deposit_object((PyObject*)op);
|
2000-04-24 23:40:53 +08:00
|
|
|
|
1993-07-28 17:05:47 +08:00
|
|
|
#ifdef __cplusplus
|
|
|
|
}
|
|
|
|
#endif
|
|
|
|
#endif /* !Py_OBJECT_H */
|