I have a really odd problem that I described here . I try to get my head around this issue and came across this in memory.h : #define NEW(t) (t*)zmalloc(sizeof(t)) #define N_NEW(n,t) (t*)gcalloc((n),sizeof(t)) #define GNEW(t) (t*)gmalloc(sizeof(t)) #define N_GNEW(n,t) (…

realloc/calloc/malloc do different things. I’m not sure about the other letters in front of the names or the macros though.

It’s not even different mallocs - I think they are just macros or functions that wrap whatever malloc is around. I realize that reliance on macros is passe and out of step with reasonable coding style today.

[image] Potential language extension for graph object classes - motivation, design It’s not so important. I will respectfully disagree with Stephen :slight_smile: Vithanco, my background is mostly C/C++ and I still had a very similar reaction to you when learning the code base. In 2020 I dele…

So many different mallocs - do we need them? - #3 by scnorth - Dev

Topic		Replies	Views	Activity
Some vmalloc questions Dev	21	883	June 3, 2020
Public API and headers again Dev	5	62	April 2, 2026
Memory leak caused by agwrite Dev	12	169	October 8, 2025
Changing the public API to use size_t? Dev	7	763	November 26, 2020
API for function `gvPluginList`: When did it change? Dev	4	95	August 12, 2025