Tim Peters | 8b078f9 | 2002-04-28 04:11:46 +0000 | [diff] [blame] | 1 | /* The PyMem_ family: low-level memory allocation interfaces. |
| 2 | See objimpl.h for the PyObject_ memory family. |
| 3 | */ |
Peter Schneider-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 4 | |
| 5 | #ifndef Py_PYMEM_H |
| 6 | #define Py_PYMEM_H |
| 7 | |
| 8 | #include "pyport.h" |
| 9 | |
| 10 | #ifdef __cplusplus |
| 11 | extern "C" { |
| 12 | #endif |
| 13 | |
Peter Schneider-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 14 | /* BEWARE: |
| 15 | |
Tim Peters | 8b078f9 | 2002-04-28 04:11:46 +0000 | [diff] [blame] | 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. |
Peter Schneider-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 21 | |
Tim Peters | 8b078f9 | 2002-04-28 04:11:46 +0000 | [diff] [blame] | 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. |
| 33 | */ |
Peter Schneider-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 34 | |
| 35 | /* |
| 36 | * Raw memory interface |
| 37 | * ==================== |
| 38 | */ |
| 39 | |
Tim Peters | 8b078f9 | 2002-04-28 04:11:46 +0000 | [diff] [blame] | 40 | /* Functions |
Peter Schneider-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 41 | |
Tim Peters | 8b078f9 | 2002-04-28 04:11:46 +0000 | [diff] [blame] | 42 | Functions supplying platform-independent semantics for malloc/realloc/ |
| 43 | free. These functions make sure that allocating 0 bytes returns a distinct |
Tim Peters | af3e8de | 2002-04-12 07:22:56 +0000 | [diff] [blame] | 44 | 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 Peters | 8b078f9 | 2002-04-28 04:11:46 +0000 | [diff] [blame] | 47 | performed on failure (no exception is set, no warning is printed, etc). |
| 48 | */ |
Tim Peters | af3e8de | 2002-04-12 07:22:56 +0000 | [diff] [blame] | 49 | |
Mark Hammond | 91a681d | 2002-08-12 07:21:58 +0000 | [diff] [blame] | 50 | PyAPI_FUNC(void *) PyMem_Malloc(size_t); |
| 51 | PyAPI_FUNC(void *) PyMem_Realloc(void *, size_t); |
| 52 | PyAPI_FUNC(void) PyMem_Free(void *); |
Peter Schneider-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 53 | |
| 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 Peters | af3e8de | 2002-04-12 07:22:56 +0000 | [diff] [blame] | 57 | /* Macros. */ |
Tim Peters | 51e7f5c | 2002-04-22 02:33:27 +0000 | [diff] [blame] | 58 | #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 Peters | 51e7f5c | 2002-04-22 02:33:27 +0000 | [diff] [blame] | 62 | |
| 63 | #else /* ! PYMALLOC_DEBUG */ |
| 64 | |
Martin v. Löwis | 39f59b0 | 2002-11-23 09:13:40 +0000 | [diff] [blame] | 65 | /* 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 Peters | af3e8de | 2002-04-12 07:22:56 +0000 | [diff] [blame] | 69 | #define PyMem_MALLOC(n) malloc((n) ? (n) : 1) |
Tim Peters | af3e8de | 2002-04-12 07:22:56 +0000 | [diff] [blame] | 70 | #define PyMem_REALLOC(p, n) realloc((p), (n) ? (n) : 1) |
| 71 | |
Tim Peters | 51e7f5c | 2002-04-22 02:33:27 +0000 | [diff] [blame] | 72 | #endif /* PYMALLOC_DEBUG */ |
Tim Peters | af3e8de | 2002-04-12 07:22:56 +0000 | [diff] [blame] | 73 | |
Tim Peters | 8b078f9 | 2002-04-28 04:11:46 +0000 | [diff] [blame] | 74 | /* 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-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 79 | /* |
| 80 | * Type-oriented memory interface |
| 81 | * ============================== |
Tim Peters | af3e8de | 2002-04-12 07:22:56 +0000 | [diff] [blame] | 82 | * |
| 83 | * These are carried along for historical reasons. There's rarely a good |
Tim Peters | 8b078f9 | 2002-04-28 04:11:46 +0000 | [diff] [blame] | 84 | * reason to use them anymore (you can just as easily do the multiply and |
| 85 | * cast yourself). |
Peter Schneider-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 86 | */ |
| 87 | |
Peter Schneider-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 88 | #define PyMem_New(type, n) \ |
| 89 | ( (type *) PyMem_Malloc((n) * sizeof(type)) ) |
Peter Schneider-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 90 | #define PyMem_NEW(type, n) \ |
Tim Peters | af3e8de | 2002-04-12 07:22:56 +0000 | [diff] [blame] | 91 | ( (type *) PyMem_MALLOC((n) * sizeof(type)) ) |
Tim Peters | 8b078f9 | 2002-04-28 04:11:46 +0000 | [diff] [blame] | 92 | |
| 93 | #define PyMem_Resize(p, type, n) \ |
| 94 | ( (p) = (type *) PyMem_Realloc((p), (n) * sizeof(type)) ) |
Tim Peters | af3e8de | 2002-04-12 07:22:56 +0000 | [diff] [blame] | 95 | #define PyMem_RESIZE(p, type, n) \ |
| 96 | ( (p) = (type *) PyMem_REALLOC((p), (n) * sizeof(type)) ) |
Tim Peters | a5d78cc | 2002-03-02 08:43:19 +0000 | [diff] [blame] | 97 | |
Tim Peters | 8b078f9 | 2002-04-28 04:11:46 +0000 | [diff] [blame] | 98 | /* 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 Peters | ddea208 | 2002-03-23 10:03:50 +0000 | [diff] [blame] | 103 | |
Peter Schneider-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 104 | #ifdef __cplusplus |
| 105 | } |
| 106 | #endif |
| 107 | |
Peter Schneider-Kamp | 25f6894 | 2000-07-31 22:19:30 +0000 | [diff] [blame] | 108 | #endif /* !Py_PYMEM_H */ |