> ALLOC_USE_MALLOC would be faster than the current pool code for > a threaded APR (but, I'm not sure). > Status: Justin volunteers > + David and Sander are working on some stuff that > + should be ready Real Soon Now (TM). Sander has > + posted a "trivial" SMS (what a bad name) - see:
Yep, in the email to the list I stated that the name wasn't good. Suggestions very welcome. Please refer to the post for naming issues. > + <[EMAIL PROTECTED]> > + which uses the same memory management as the current > + pool implementation (freelist that allocates > any size). > + David is finishing up prototyping a replacement for > + apr_pool_t that is defined as an SMS (I believe it is > + API-compatible). Not ready for prime-time, but ready > + for us to start working out the kinks and actually > + starting to use SMS. Sander
