Allow custom memory management #11
Conversation
francisbouvier
force-pushed
the
custom_memory
branch
from
b17255c
to
2625bfa
Compare
src/utils/utils.c
Outdated
| { | ||
| return (*my_calloc)(elementCount, size); | ||
| }; | ||
| void _free(void *ptr) |
There was a problem hiding this comment.
Why we have no *_ prefix here? And what does the *_ prefix mean?
There was a problem hiding this comment.
* is just to say it's pointer. free signature in C is void free(void *ptr) so we do not need a pointer here. You can write type* value, type * value or type *value, it's the same.
Personnaly I prefer the first version as it's more clear that the type is a pointer, but netsurf is using the last one so I tried to stick to this style.
Regarding the _ it's just the name I choose for the custom calls. I could have choose whatever name, as long as I'm using it in the macro #define free(ptr) _free(ptr)
There was a problem hiding this comment.
oh ok 🤦 I was confused with the void * in fact, I did'nt realize it's a any pointer type...
francisbouvier
force-pushed
the
custom_memory
branch
from
2625bfa
to
2507f64
Compare
Provides functions to replace standard malloc/calloc/realloc/free Signed-off-by: Francis Bouvier <[email protected]>
francisbouvier
force-pushed
the
custom_memory
branch
from
2507f64
to
6c87ab8
Compare
Provides functions to replace standard malloc/calloc/realloc/free
Closes #8