> Of course, for short-running programs, just malloc, don't free, is the fastest.
A custom malloc that knew free would never be called would be faster still. I wonder if any short-running utilities do this?
A custom malloc that knew free would never be called would be faster still. I wonder if any short-running utilities do this?