Stuart Reynolds wrote:
For our own interrnal uses of STL we provide our own STL allocators, which resolve to malloc/free callback functions provided to our library through its public interface. However, without recompiling the source to the serialization library, I don't think I can make the library use these allocators. (Right?)
Right
Generally speaking, because I work on embedded systems, we need to monitor and control memory usage very carefully. We can't have any dependencies on libraries that make naked calls to malloc/free or global new/delete since on many of the platforms we target the OS does not provide a heap, or must use a particular one of manys available heaps each of which may reference physically different memory.
If all allocations went to boost::archive::details::heap_allocator<>,
they don't. heap allocator is used only for resurrection objects saved through pointers.
So, for now it looks like I need to modify the the serialization library for boost and incorporate it into my build system. (Right?)
Right Robert Ramey