blob: dfdbca079af4373a8a4b179de73b66ea18cd3914 [file] [log] [blame]
Guido van Rossumf70e43a1991-02-19 12:39:46 +00001/***********************************************************
Guido van Rossumfd71b9e2000-06-30 23:50:40 +00002Copyright (c) 2000, BeOpen.com.
3Copyright (c) 1995-2000, Corporation for National Research Initiatives.
4Copyright (c) 1990-1995, Stichting Mathematisch Centrum.
5All rights reserved.
Guido van Rossumf70e43a1991-02-19 12:39:46 +00006
Guido van Rossumfd71b9e2000-06-30 23:50:40 +00007See the file "Misc/COPYRIGHT" for information on usage and
8redistribution of this file, and for a DISCLAIMER OF ALL WARRANTIES.
Guido van Rossumf70e43a1991-02-19 12:39:46 +00009******************************************************************/
10
Fred Drake3cf4d2b2000-07-09 00:55:06 +000011#ifndef Py_OBJIMPL_H
12#define Py_OBJIMPL_H
13#ifdef __cplusplus
14extern "C" {
15#endif
16
Guido van Rossumb18618d2000-05-03 23:44:39 +000017#include "mymalloc.h"
18
Guido van Rossum85a5fbb1990-10-14 12:07:46 +000019/*
Guido van Rossumb18618d2000-05-03 23:44:39 +000020Functions and macros for modules that implement new object types.
Guido van Rossum85a5fbb1990-10-14 12:07:46 +000021You must first include "object.h".
22
Guido van Rossumb18618d2000-05-03 23:44:39 +000023 - PyObject_New(type, typeobj) allocates memory for a new object of
24 the given type; here 'type' must be the C structure type used to
25 represent the object and 'typeobj' the address of the corresponding
26 type object. Reference count and type pointer are filled in; the
27 rest of the bytes of the object are *undefined*! The resulting
28 expression type is 'type *'. The size of the object is actually
29 determined by the tp_basicsize field of the type object.
Guido van Rossum85a5fbb1990-10-14 12:07:46 +000030
Guido van Rossumb18618d2000-05-03 23:44:39 +000031 - PyObject_NewVar(type, typeobj, n) is similar but allocates a
32 variable-size object with n extra items. The size is computed as
33 tp_basicsize plus n * tp_itemsize. This fills in the ob_size field
34 as well.
Guido van Rossum85a5fbb1990-10-14 12:07:46 +000035
Guido van Rossumb18618d2000-05-03 23:44:39 +000036 - PyObject_Del(op) releases the memory allocated for an object.
37
38 - PyObject_Init(op, typeobj) and PyObject_InitVar(op, typeobj, n) are
39 similar to PyObject_{New, NewVar} except that they don't allocate
40 the memory needed for an object. Instead of the 'type' parameter,
41 they accept the pointer of a new object (allocated by an arbitrary
42 allocator) and initialize its object header fields.
43
44Note that objects created with PyObject_{New, NewVar} are allocated
45within the Python heap by an object allocator, the latter being
46implemented (by default) on top of the Python raw memory
47allocator. This ensures that Python keeps control on the user's
48objects regarding their memory management; for instance, they may be
49subject to automatic garbage collection.
50
51In case a specific form of memory management is needed, implying that
52the objects would not reside in the Python heap (for example standard
53malloc heap(s) are mandatory, use of shared memory, C++ local storage
54or operator new), you must first allocate the object with your custom
55allocator, then pass its pointer to PyObject_{Init, InitVar} for
56filling in its Python-specific fields: reference count, type pointer,
57possibly others. You should be aware that Python has very limited
58control over these objects because they don't cooperate with the
59Python memory manager. Such objects may not be eligible for automatic
60garbage collection and you have to make sure that they are released
61accordingly whenever their destructor gets called (cf. the specific
62form of memory management you're using).
63
64Unless you have specific memory management requirements, it is
65recommended to use PyObject_{New, NewVar, Del}. */
66
67/*
68 * Core object memory allocator
69 * ============================
70 */
71
Vladimir Marangozovd8a93322000-07-10 04:30:56 +000072/* The purpose of the object allocator is to make the distinction
Guido van Rossumb18618d2000-05-03 23:44:39 +000073 between "object memory" and the rest within the Python heap.
74
75 Object memory is the one allocated by PyObject_{New, NewVar}, i.e.
76 the one that holds the object's representation defined by its C
77 type structure, *excluding* any object-specific memory buffers that
78 might be referenced by the structure (for type structures that have
79 pointer fields). By default, the object memory allocator is
80 implemented on top of the raw memory allocator.
81
82 The PyCore_* macros can be defined to make the interpreter use a
83 custom object memory allocator. They are reserved for internal
84 memory management purposes exclusively. Both the core and extension
85 modules should use the PyObject_* API. */
86
87#ifndef PyCore_OBJECT_MALLOC_FUNC
88#undef PyCore_OBJECT_REALLOC_FUNC
89#undef PyCore_OBJECT_FREE_FUNC
90#define PyCore_OBJECT_MALLOC_FUNC PyCore_MALLOC_FUNC
91#define PyCore_OBJECT_REALLOC_FUNC PyCore_REALLOC_FUNC
92#define PyCore_OBJECT_FREE_FUNC PyCore_FREE_FUNC
93#endif
94
95#ifndef PyCore_OBJECT_MALLOC_PROTO
96#undef PyCore_OBJECT_REALLOC_PROTO
97#undef PyCore_OBJECT_FREE_PROTO
98#define PyCore_OBJECT_MALLOC_PROTO PyCore_MALLOC_PROTO
99#define PyCore_OBJECT_REALLOC_PROTO PyCore_REALLOC_PROTO
100#define PyCore_OBJECT_FREE_PROTO PyCore_FREE_PROTO
101#endif
102
103#ifdef NEED_TO_DECLARE_OBJECT_MALLOC_AND_FRIEND
Thomas Wouters334fb892000-07-25 12:56:38 +0000104extern void *PyCore_OBJECT_MALLOC_FUNC PyCore_OBJECT_MALLOC_PROTO;
105extern void *PyCore_OBJECT_REALLOC_FUNC PyCore_OBJECT_REALLOC_PROTO;
Guido van Rossumb18618d2000-05-03 23:44:39 +0000106extern void PyCore_OBJECT_FREE_FUNC PyCore_OBJECT_FREE_PROTO;
107#endif
108
109#ifndef PyCore_OBJECT_MALLOC
110#undef PyCore_OBJECT_REALLOC
111#undef PyCore_OBJECT_FREE
112#define PyCore_OBJECT_MALLOC(n) PyCore_OBJECT_MALLOC_FUNC(n)
113#define PyCore_OBJECT_REALLOC(p, n) PyCore_OBJECT_REALLOC_FUNC((p), (n))
114#define PyCore_OBJECT_FREE(p) PyCore_OBJECT_FREE_FUNC(p)
115#endif
116
117/*
118 * Raw object memory interface
119 * ===========================
120 */
121
122/* The use of this API should be avoided, unless a builtin object
123 constructor inlines PyObject_{New, NewVar}, either because the
124 latter functions cannot allocate the exact amount of needed memory,
125 either for speed. This situation is exceptional, but occurs for
126 some object constructors (PyBuffer_New, PyList_New...). Inlining
127 PyObject_{New, NewVar} for objects that are supposed to belong to
128 the Python heap is discouraged. If you really have to, make sure
129 the object is initialized with PyObject_{Init, InitVar}. Do *not*
130 inline PyObject_{Init, InitVar} for user-extension types or you
131 might seriously interfere with Python's memory management. */
132
133/* Functions */
134
135/* Wrappers around PyCore_OBJECT_MALLOC and friends; useful if you
136 need to be sure that you are using the same object memory allocator
137 as Python. These wrappers *do not* make sure that allocating 0
138 bytes returns a non-NULL pointer. Returned pointers must be checked
139 for NULL explicitly; no action is performed on failure. */
Thomas Wouters334fb892000-07-25 12:56:38 +0000140extern DL_IMPORT(void *) PyObject_Malloc(size_t);
141extern DL_IMPORT(void *) PyObject_Realloc(void *, size_t);
142extern DL_IMPORT(void) PyObject_Free(void *);
Guido van Rossumb18618d2000-05-03 23:44:39 +0000143
144/* Macros */
145#define PyObject_MALLOC(n) PyCore_OBJECT_MALLOC(n)
Thomas Wouters334fb892000-07-25 12:56:38 +0000146#define PyObject_REALLOC(op, n) PyCore_OBJECT_REALLOC((void *)(op), (n))
147#define PyObject_FREE(op) PyCore_OBJECT_FREE((void *)(op))
Guido van Rossumb18618d2000-05-03 23:44:39 +0000148
149/*
150 * Generic object allocator interface
151 * ==================================
152 */
153
154/* Functions */
Fred Drake3cf4d2b2000-07-09 00:55:06 +0000155extern DL_IMPORT(PyObject *) PyObject_Init(PyObject *, PyTypeObject *);
156extern DL_IMPORT(PyVarObject *) PyObject_InitVar(PyVarObject *,
157 PyTypeObject *, int);
158extern DL_IMPORT(PyObject *) _PyObject_New(PyTypeObject *);
159extern DL_IMPORT(PyVarObject *) _PyObject_NewVar(PyTypeObject *, int);
160extern DL_IMPORT(void) _PyObject_Del(PyObject *);
Guido van Rossum85a5fbb1990-10-14 12:07:46 +0000161
Guido van Rossumb18618d2000-05-03 23:44:39 +0000162#define PyObject_New(type, typeobj) \
163 ( (type *) _PyObject_New(typeobj) )
164#define PyObject_NewVar(type, typeobj, n) \
165 ( (type *) _PyObject_NewVar((typeobj), (n)) )
166#define PyObject_Del(op) _PyObject_Del((PyObject *)(op))
Guido van Rossuma3309961993-07-28 09:05:47 +0000167
Guido van Rossumb18618d2000-05-03 23:44:39 +0000168/* Macros trading binary compatibility for speed. See also mymalloc.h.
169 Note that these macros expect non-NULL object pointers.*/
170#define PyObject_INIT(op, typeobj) \
171 ( (op)->ob_type = (typeobj), _Py_NewReference((PyObject *)(op)), (op) )
172#define PyObject_INIT_VAR(op, typeobj, size) \
173 ( (op)->ob_size = (size), PyObject_INIT((op), (typeobj)) )
Guido van Rossum5a849141996-07-21 02:23:54 +0000174
Guido van Rossumb18618d2000-05-03 23:44:39 +0000175#define _PyObject_SIZE(typeobj) ( (typeobj)->tp_basicsize )
176#define _PyObject_VAR_SIZE(typeobj, n) \
177 ( (typeobj)->tp_basicsize + (n) * (typeobj)->tp_itemsize )
Guido van Rossum5a849141996-07-21 02:23:54 +0000178
Guido van Rossumb18618d2000-05-03 23:44:39 +0000179#define PyObject_NEW(type, typeobj) \
180( (type *) PyObject_Init( \
181 (PyObject *) PyObject_MALLOC( _PyObject_SIZE(typeobj) ), (typeobj)) )
182#define PyObject_NEW_VAR(type, typeobj, n) \
183( (type *) PyObject_InitVar( \
184 (PyVarObject *) PyObject_MALLOC( _PyObject_VAR_SIZE((typeobj),(n)) ),\
185 (typeobj), (n)) )
Guido van Rossumb18618d2000-05-03 23:44:39 +0000186
Guido van Rossum4cc6ac72000-07-01 01:00:38 +0000187#define PyObject_DEL(op) PyObject_FREE(op)
188
Guido van Rossumb18618d2000-05-03 23:44:39 +0000189/* This example code implements an object constructor with a custom
190 allocator, where PyObject_New is inlined, and shows the important
191 distinction between two steps (at least):
192 1) the actual allocation of the object storage;
193 2) the initialization of the Python specific fields
194 in this storage with PyObject_{Init, InitVar}.
195
196 PyObject *
197 YourObject_New(...)
198 {
199 PyObject *op;
200
201 op = (PyObject *) Your_Allocator(_PyObject_SIZE(YourTypeStruct));
202 if (op == NULL)
203 return PyErr_NoMemory();
204
205 op = PyObject_Init(op, &YourTypeStruct);
206 if (op == NULL)
207 return NULL;
208
209 op->ob_field = value;
210 ...
211 return op;
212 }
213
214 Note that in C++, the use of the new operator usually implies that
215 the 1st step is performed automatically for you, so in a C++ class
216 constructor you would start directly with PyObject_Init/InitVar. */
Guido van Rossum5a849141996-07-21 02:23:54 +0000217
Jeremy Hyltonc5007aa2000-06-30 05:02:53 +0000218/*
219 * Garbage Collection Support
220 * ==========================
221 */
Jeremy Hyltond08b4c42000-06-23 19:37:02 +0000222
Jeremy Hyltonc5007aa2000-06-30 05:02:53 +0000223/* To make a new object participate in garbage collection use
224 PyObject_{New, VarNew, Del} to manage the memory. Set the type flag
225 Py_TPFLAGS_GC and define the type method tp_recurse. You should also
226 add the method tp_clear if your object is mutable. Include
Guido van Rossum4cc6ac72000-07-01 01:00:38 +0000227 PyGC_HEAD_SIZE in the calculation of tp_basicsize. Call
Jeremy Hyltonc5007aa2000-06-30 05:02:53 +0000228 PyObject_GC_Init after the pointers followed by tp_recurse become
229 valid (usually just before returning the object from the allocation
230 method. Call PyObject_GC_Fini before those pointers become invalid
231 (usually at the top of the deallocation method). */
Jeremy Hyltond08b4c42000-06-23 19:37:02 +0000232
233#ifndef WITH_CYCLE_GC
Jeremy Hyltonc5007aa2000-06-30 05:02:53 +0000234
235#define PyGC_HEAD_SIZE 0
236#define PyObject_GC_Init(op)
237#define PyObject_GC_Fini(op)
238#define PyObject_AS_GC(op) (op)
239#define PyObject_FROM_GC(op) (op)
Jeremy Hyltonc5007aa2000-06-30 05:02:53 +0000240
241#else
242
243/* Add the object into the container set */
Fred Drake3cf4d2b2000-07-09 00:55:06 +0000244extern DL_IMPORT(void) _PyGC_Insert(PyObject *);
Jeremy Hyltonc5007aa2000-06-30 05:02:53 +0000245
246/* Remove the object from the container set */
Fred Drake3cf4d2b2000-07-09 00:55:06 +0000247extern DL_IMPORT(void) _PyGC_Remove(PyObject *);
Jeremy Hyltonc5007aa2000-06-30 05:02:53 +0000248
249#define PyObject_GC_Init(op) _PyGC_Insert((PyObject *)op)
250#define PyObject_GC_Fini(op) _PyGC_Remove((PyObject *)op)
251
252/* Structure *prefixed* to container objects participating in GC */
253typedef struct _gc_head {
254 struct _gc_head *gc_next;
255 struct _gc_head *gc_prev;
256 int gc_refs;
257} PyGC_Head;
258
259#define PyGC_HEAD_SIZE sizeof(PyGC_Head)
260
261/* Test if a type has a GC head */
262#define PyType_IS_GC(t) PyType_HasFeature((t), Py_TPFLAGS_GC)
263
264/* Test if an object has a GC head */
265#define PyObject_IS_GC(o) PyType_IS_GC((o)->ob_type)
266
267/* Get an object's GC head */
268#define PyObject_AS_GC(o) ((PyGC_Head *)(o)-1)
269
270/* Get the object given the PyGC_Head */
271#define PyObject_FROM_GC(g) ((PyObject *)(((PyGC_Head *)g)+1))
272
Jeremy Hyltonc5007aa2000-06-30 05:02:53 +0000273#endif /* WITH_CYCLE_GC */
Jeremy Hyltond08b4c42000-06-23 19:37:02 +0000274
Guido van Rossuma3309961993-07-28 09:05:47 +0000275#ifdef __cplusplus
276}
277#endif
278#endif /* !Py_OBJIMPL_H */