blob: f8aef2991bcebe17c7fd65431a0753b0a18aa1e9 [file] [log] [blame]
Tim Peters8b078f92002-04-28 04:11:46 +00001/* The PyMem_ family: low-level memory allocation interfaces.
2 See objimpl.h for the PyObject_ memory family.
3*/
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +00004
5#ifndef Py_PYMEM_H
6#define Py_PYMEM_H
7
8#include "pyport.h"
9
10#ifdef __cplusplus
11extern "C" {
12#endif
13
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +000014/* BEWARE:
15
Tim Peters8b078f92002-04-28 04:11:46 +000016 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.
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +000021
Tim Peters8b078f92002-04-28 04:11:46 +000022 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.
33*/
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +000034
35/*
36 * Raw memory interface
37 * ====================
38 */
39
Tim Peters8b078f92002-04-28 04:11:46 +000040/* Functions
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +000041
Tim Peters8b078f92002-04-28 04:11:46 +000042 Functions supplying platform-independent semantics for malloc/realloc/
43 free. These functions make sure that allocating 0 bytes returns a distinct
Tim Petersaf3e8de2002-04-12 07:22:56 +000044 non-NULL pointer (whenever possible -- if we're flat out of memory, NULL
45 may be returned), even if the platform malloc and realloc don't.
46 Returned pointers must be checked for NULL explicitly. No action is
Tim Peters8b078f92002-04-28 04:11:46 +000047 performed on failure (no exception is set, no warning is printed, etc).
48*/
Tim Petersaf3e8de2002-04-12 07:22:56 +000049
Mark Hammond91a681d2002-08-12 07:21:58 +000050PyAPI_FUNC(void *) PyMem_Malloc(size_t);
51PyAPI_FUNC(void *) PyMem_Realloc(void *, size_t);
52PyAPI_FUNC(void) PyMem_Free(void *);
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +000053
54/* Starting from Python 1.6, the wrappers Py_{Malloc,Realloc,Free} are
55 no longer supported. They used to call PyErr_NoMemory() on failure. */
56
Tim Petersaf3e8de2002-04-12 07:22:56 +000057/* Macros. */
Tim Peters51e7f5c2002-04-22 02:33:27 +000058#ifdef PYMALLOC_DEBUG
59/* Redirect all memory operations to Python's debugging allocator. */
60#define PyMem_MALLOC PyObject_MALLOC
61#define PyMem_REALLOC PyObject_REALLOC
Tim Peters51e7f5c2002-04-22 02:33:27 +000062
63#else /* ! PYMALLOC_DEBUG */
64
Martin v. Löwis39f59b02002-11-23 09:13:40 +000065/* PyMem_MALLOC(0) means malloc(1). Some systems would return NULL
66 for malloc(0), which would be treated as an error. Some platforms
67 would return a pointer with no memory behind it, which would break
68 pymalloc. To solve these problems, allocate an extra byte. */
Tim Petersaf3e8de2002-04-12 07:22:56 +000069#define PyMem_MALLOC(n) malloc((n) ? (n) : 1)
Tim Petersaf3e8de2002-04-12 07:22:56 +000070#define PyMem_REALLOC(p, n) realloc((p), (n) ? (n) : 1)
71
Tim Peters51e7f5c2002-04-22 02:33:27 +000072#endif /* PYMALLOC_DEBUG */
Tim Petersaf3e8de2002-04-12 07:22:56 +000073
Tim Peters8b078f92002-04-28 04:11:46 +000074/* In order to avoid breaking old code mixing PyObject_{New, NEW} with
75 PyMem_{Del, DEL} and PyMem_{Free, FREE}, the PyMem "release memory"
76 functions have to be redirected to the object deallocator. */
77#define PyMem_FREE PyObject_FREE
78
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +000079/*
80 * Type-oriented memory interface
81 * ==============================
Tim Petersaf3e8de2002-04-12 07:22:56 +000082 *
83 * These are carried along for historical reasons. There's rarely a good
Tim Peters8b078f92002-04-28 04:11:46 +000084 * reason to use them anymore (you can just as easily do the multiply and
85 * cast yourself).
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +000086 */
87
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +000088#define PyMem_New(type, n) \
89 ( (type *) PyMem_Malloc((n) * sizeof(type)) )
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +000090#define PyMem_NEW(type, n) \
Tim Petersaf3e8de2002-04-12 07:22:56 +000091 ( (type *) PyMem_MALLOC((n) * sizeof(type)) )
Tim Peters8b078f92002-04-28 04:11:46 +000092
93#define PyMem_Resize(p, type, n) \
94 ( (p) = (type *) PyMem_Realloc((p), (n) * sizeof(type)) )
Tim Petersaf3e8de2002-04-12 07:22:56 +000095#define PyMem_RESIZE(p, type, n) \
96 ( (p) = (type *) PyMem_REALLOC((p), (n) * sizeof(type)) )
Tim Petersa5d78cc2002-03-02 08:43:19 +000097
Tim Peters8b078f92002-04-28 04:11:46 +000098/* In order to avoid breaking old code mixing PyObject_{New, NEW} with
99 PyMem_{Del, DEL} and PyMem_{Free, FREE}, the PyMem "release memory"
100 functions have to be redirected to the object deallocator. */
101#define PyMem_Del PyObject_Free
102#define PyMem_DEL PyObject_FREE
Tim Petersddea2082002-03-23 10:03:50 +0000103
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +0000104#ifdef __cplusplus
105}
106#endif
107
Peter Schneider-Kamp25f68942000-07-31 22:19:30 +0000108#endif /* !Py_PYMEM_H */