From: Claudio V. C. <cv...@us...> - 2002-10-13 00:55:56
|
> -----Original Message----- > From: fir...@li... > [mailto:fir...@li...]On Behalf Of John > Bellardo > Sent: Viernes 11 de Octubre de 2002 11:26 > > >> You MUST allocate all memory from a pool. Don't use the default > >> global new(). > >> [...] > > The original intent for that message turned out to be too aggressive. > That functionality should just be dropped. It is ~5 lines in two > places in the file src/common/memory/allocators.cpp. Search for > "printf" and you should be able to find it. Can you explain more? Are you saying that it doesn't matter whether memory comes from the allocator or comes directly from the heap used by the "new" operator? I thought all memory inside the engine would be managed by the allocators. But if some implementations use the original new operator, probably it happens inside units where our changed operator isn't visible. Is this the problem? C. |