On Mon, 16 Feb 2009 08:06:11 +0100 Mladen Turk <[email protected]> wrote:
> One thing I've proposed (but was vetoed) was the actual > malloc/free programmable replacement within the allocator. > Now the thing to consider is to make the allocator public > allowing to implement what ever system memory allocation > there is (eg, heap or virtualmemory on win32, shm, etc) > instead just relying on standard allocator implementation > which (I presume that 8K granulation was more or less > empirically determined) is fixed. Can you point to that discussion? Seems to me that if it can be done without performance penalties, then making the allocator into a public API should have potential to be the solution to make everyone happy. -- Nick Kew
