Originally Posted By: Superku
...
I assume sys_malloc just calls malloc and adds a few security and error handling "systems" (including the very useful sys_marker instruction that is not supported by the default malloc instruction).


Yes and because of that a direct malloc call is faster than sys_malloc.
But hey we are in C. If its not neccesary to build large arrays or objects at each engineframe I wouldnt care.

Ullllillia would create a benchmark for that and would us overheap with numbers.


"Make a great game or kill it early" (Bruce Shelley, Ensemble Studios)