mirror of
https://github.com/python/cpython.git
synced 2025-07-30 06:34:15 +00:00
ee3a1b5244
of some of the common builtin types. Use a bit in tp_flags for each common builtin type. Check the bit to determine if any instance is a subclass of these common types. The check avoids a function call and O(n) search of the base classes. The check is done in the various Py*_Check macros rather than calling PyType_IsSubtype(). All the bits are set in tp_flags when the type is declared in the Objects/*object.c files because PyType_Ready() is not called for all the types. Should PyType_Ready() be called for all types? If so and the change is made, the changes to the Objects/*object.c files can be reverted (remove setting the tp_flags). Objects/typeobject.c would also have to be modified to add conditions for Py*_CheckExact() in addition to each the PyType_IsSubtype check.
58 lines
2.1 KiB
C
58 lines
2.1 KiB
C
|
|
/* Tuple object interface */
|
|
|
|
#ifndef Py_TUPLEOBJECT_H
|
|
#define Py_TUPLEOBJECT_H
|
|
#ifdef __cplusplus
|
|
extern "C" {
|
|
#endif
|
|
|
|
/*
|
|
Another generally useful object type is a tuple of object pointers.
|
|
For Python, this is an immutable type. C code can change the tuple items
|
|
(but not their number), and even use tuples are general-purpose arrays of
|
|
object references, but in general only brand new tuples should be mutated,
|
|
not ones that might already have been exposed to Python code.
|
|
|
|
*** WARNING *** PyTuple_SetItem does not increment the new item's reference
|
|
count, but does decrement the reference count of the item it replaces,
|
|
if not nil. It does *decrement* the reference count if it is *not*
|
|
inserted in the tuple. Similarly, PyTuple_GetItem does not increment the
|
|
returned item's reference count.
|
|
*/
|
|
|
|
typedef struct {
|
|
PyObject_VAR_HEAD
|
|
PyObject *ob_item[1];
|
|
|
|
/* ob_item contains space for 'ob_size' elements.
|
|
* Items must normally not be NULL, except during construction when
|
|
* the tuple is not yet visible outside the function that builds it.
|
|
*/
|
|
} PyTupleObject;
|
|
|
|
PyAPI_DATA(PyTypeObject) PyTuple_Type;
|
|
|
|
#define PyTuple_Check(op) \
|
|
PyType_FastSubclass((op)->ob_type, Py_TPFLAGS_TUPLE_SUBCLASS)
|
|
#define PyTuple_CheckExact(op) ((op)->ob_type == &PyTuple_Type)
|
|
|
|
PyAPI_FUNC(PyObject *) PyTuple_New(Py_ssize_t size);
|
|
PyAPI_FUNC(Py_ssize_t) PyTuple_Size(PyObject *);
|
|
PyAPI_FUNC(PyObject *) PyTuple_GetItem(PyObject *, Py_ssize_t);
|
|
PyAPI_FUNC(int) PyTuple_SetItem(PyObject *, Py_ssize_t, PyObject *);
|
|
PyAPI_FUNC(PyObject *) PyTuple_GetSlice(PyObject *, Py_ssize_t, Py_ssize_t);
|
|
PyAPI_FUNC(int) _PyTuple_Resize(PyObject **, Py_ssize_t);
|
|
PyAPI_FUNC(PyObject *) PyTuple_Pack(Py_ssize_t, ...);
|
|
|
|
/* Macro, trading safety for speed */
|
|
#define PyTuple_GET_ITEM(op, i) (((PyTupleObject *)(op))->ob_item[i])
|
|
#define PyTuple_GET_SIZE(op) (((PyTupleObject *)(op))->ob_size)
|
|
|
|
/* Macro, *only* to be used to fill in brand new tuples */
|
|
#define PyTuple_SET_ITEM(op, i, v) (((PyTupleObject *)(op))->ob_item[i] = v)
|
|
|
|
#ifdef __cplusplus
|
|
}
|
|
#endif
|
|
#endif /* !Py_TUPLEOBJECT_H */
|