https://svn.boost.org/trac10/ticket/9052 <p> Currently it's not possible to avoid allocations from happening with the standard allocators of the used standard library. </p> <p> That makes it quite impossible to manage the memory for the parser. </p> <p> Some use case examples: </p> <ul><li>Writing a library in C++ with a C interface allowing the user to pass 'malloc' and 'free' replacements. </li><li>Writing a program that uses a pool memory allocator </li></ul><p> I know that this probably won't be too high on your todo list, however it'd be great to have. </p> en-us /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/9052 Trac 1.4.3 evilissimo@… Tue, 27 Aug 2013 14:45:56 GMT https://svn.boost.org/trac10/ticket/9052 https://svn.boost.org/trac10/ticket/9052 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">allocator_support.patch</span> </li> </ul> <p> A potential solution to support allocators on rule and grammar </p> Ticket