Revert part of r60927 which made invalid assumptions about the API offered by db...
[python.git] / Include / pymem.h
blob7f74f3701b0a78fd39720077ec983e3c2d039780
1 /* The PyMem_ family: low-level memory allocation interfaces.
2 See objimpl.h for the PyObject_ memory family.
3 */
5 #ifndef Py_PYMEM_H
6 #define Py_PYMEM_H
8 #include "pyport.h"
10 #ifdef __cplusplus
11 extern "C" {
12 #endif
14 /* BEWARE:
16 Each interface exports both functions and macros. Extension modules should
17 use the functions, to ensure binary compatibility across Python versions.
18 Because the Python implementation is free to change internal details, and
19 the macros may (or may not) expose details for speed, if you do use the
20 macros you must recompile your extensions with each Python release.
22 Never mix calls to PyMem_ with calls to the platform malloc/realloc/
23 calloc/free. For example, on Windows different DLLs may end up using
24 different heaps, and if you use PyMem_Malloc you'll get the memory from the
25 heap used by the Python DLL; it could be a disaster if you free()'ed that
26 directly in your own extension. Using PyMem_Free instead ensures Python
27 can return the memory to the proper heap. As another example, in
28 PYMALLOC_DEBUG mode, Python wraps all calls to all PyMem_ and PyObject_
29 memory functions in special debugging wrappers that add additional
30 debugging info to dynamic memory blocks. The system routines have no idea
31 what to do with that stuff, and the Python wrappers have no idea what to do
32 with raw blocks obtained directly by the system routines then.
34 The GIL must be held when using these APIs.
38 * Raw memory interface
39 * ====================
42 /* Functions
44 Functions supplying platform-independent semantics for malloc/realloc/
45 free. These functions make sure that allocating 0 bytes returns a distinct
46 non-NULL pointer (whenever possible -- if we're flat out of memory, NULL
47 may be returned), even if the platform malloc and realloc don't.
48 Returned pointers must be checked for NULL explicitly. No action is
49 performed on failure (no exception is set, no warning is printed, etc).
52 PyAPI_FUNC(void *) PyMem_Malloc(size_t);
53 PyAPI_FUNC(void *) PyMem_Realloc(void *, size_t);
54 PyAPI_FUNC(void) PyMem_Free(void *);
56 /* Starting from Python 1.6, the wrappers Py_{Malloc,Realloc,Free} are
57 no longer supported. They used to call PyErr_NoMemory() on failure. */
59 /* Macros. */
60 #ifdef PYMALLOC_DEBUG
61 /* Redirect all memory operations to Python's debugging allocator. */
62 #define PyMem_MALLOC PyObject_MALLOC
63 #define PyMem_REALLOC PyObject_REALLOC
64 #define PyMem_FREE PyObject_FREE
66 #else /* ! PYMALLOC_DEBUG */
68 /* PyMem_MALLOC(0) means malloc(1). Some systems would return NULL
69 for malloc(0), which would be treated as an error. Some platforms
70 would return a pointer with no memory behind it, which would break
71 pymalloc. To solve these problems, allocate an extra byte. */
72 #define PyMem_MALLOC(n) malloc((n) ? (n) : 1)
73 #define PyMem_REALLOC(p, n) realloc((p), (n) ? (n) : 1)
74 #define PyMem_FREE free
76 #endif /* PYMALLOC_DEBUG */
79 * Type-oriented memory interface
80 * ==============================
82 * These are carried along for historical reasons. There's rarely a good
83 * reason to use them anymore (you can just as easily do the multiply and
84 * cast yourself).
87 #define PyMem_New(type, n) \
88 ( (type *) PyMem_Malloc((n) * sizeof(type)) )
89 #define PyMem_NEW(type, n) \
90 ( (type *) PyMem_MALLOC((n) * sizeof(type)) )
92 #define PyMem_Resize(p, type, n) \
93 ( (p) = (type *) PyMem_Realloc((p), (n) * sizeof(type)) )
94 #define PyMem_RESIZE(p, type, n) \
95 ( (p) = (type *) PyMem_REALLOC((p), (n) * sizeof(type)) )
97 /* PyMem{Del,DEL} are left over from ancient days, and shouldn't be used
98 * anymore. They're just confusing aliases for PyMem_{Free,FREE} now.
100 #define PyMem_Del PyMem_Free
101 #define PyMem_DEL PyMem_FREE
103 #ifdef __cplusplus
105 #endif
107 #endif /* !Py_PYMEM_H */