Tim Peters <tim.one@comcast.net> writes: > In the other direction, e.g., > > PyObject_New -> > _PyObject_New -> > PyObject_MALLOC -> > PyCore_OBJECT_MALLOC -> > PyCore_OBJECT_MALLOC_FUNC, > and we're back in the macro chain traced above > > There's just no sane way to say "give me obmalloc.c's malloc". I may be missing something, but won't PyObject_Malloc (or PyObject_MALLOC if you prefer macros) have precisely this effect? It's the object allocator you are then talking to (and I withdraw my earlier claim that nobody wants to call this directly). Regards, Martin
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4