I'm glad to say that now "GC Allocator" is a sandbox library of boost. To gain the source code, please svn checkout http://svn.boost.org/svn/boost/sandbox/memory/. Examples: - simple_examples.cpp<http://svn.boost.org/svn/boost/sandbox/memory/libs/memory/test/memory/simple_examples.cpp> - stl_containers.cpp<http://svn.boost.org/svn/boost/sandbox/memory/libs/memory/test/memory/stl_containers.cpp> Welcome to give me some suggestions or report defects. I'm a beginner of boost development. And I don't know the process of boost peer review, and how a library is accepted (upgraded). Anyone can help me? On Fri, Apr 25, 2008 at 9:55 PM, <Lance.Diduck@ubs.com> wrote:
I think the best thing to do is package up your allocators, and present them for a boost peer review. I have a strong interest in seeing more specialty allocators in C++ so I will be glad to help, and even donate some of my own, as I am sure others would to. Even bringing up HeapLayers to boost quality standards would be worthwhile.
There are lots of ways of getting C++ classes and libraries to use specialty allocators, but hardly any allocators nor docs on why you might want to. Nor ways to actually write an allocator that could be used in a library. For some reason people attach a lot of unwarranted hype to GC and allocators -- esp to try and sell new "revolutionary" programming models. Sigh. All we really need is a library of allocators and ways to apply them without getting in trouble, and keep them out of sight when I don't care. That is all the innovation I want.