So you want custom allocator support in your C library
(nullprogram.com)
from tedu@azorius.net to programming@azorius.net on 19 Dec 2023 21:45
https://azorius.net/g/programming/p/xP4SGKcD9kC5y1lP56-So-you-want-custom-allocator-support-in-your-C-l
from tedu@azorius.net to programming@azorius.net on 19 Dec 2023 21:45
https://azorius.net/g/programming/p/xP4SGKcD9kC5y1lP56-So-you-want-custom-allocator-support-in-your-C-l
Users of mature C libraries conventionally get to choose how memory is allocated — that is, when it cannot be avoided entirely. The C standard never laid down a convention — perhaps for the better — so each library re-invents an allocator interface. Not all are created equal, and most repeat a few fundamental mistakes. Often the interface is merely a token effort, to check off that it’s “supported” without actual consideration to its use. This article describes the critical features of a practical allocator interface, and demonstrates why they’re important.
#c #malloc #programming
threaded - newest