Alas, I do need a full-fledged pool interface (in fact, I need it to be
the same pool interface so I can hand it wrapped in an apr_pool_t to
apr_hash_create and the like.
Aaron Bannert wrote:
If you don't need a full-fledged pool interface, but just malloc/free,
take a look at apr_rmm.h (in apr-util/include/). There's also an
exmaple in the apr-util examples, IIRC.
-aaron
On Friday, September 12, 2003, at 11:43 AM, Chris Knight wrote:
(If this has been discussed previously, I apologize. Is there an
archive for this mailing list somewhere?)
I would like to use the multitude of apr tools (hashes, lists, etc)
to interact with shared memory, but alas it appears there's no way to
do so (as I can't implement my own allocator.) Am I incorrect in this
assessment (and if so, how would I create a pool on top of shared
memory?) If I am correct, would providing such an interface be
generally useful and a good/bad idea?
