> this would make mem_realloc and Parrot_reallocate_buffer a little bit more > difficult, since they'd have to allocate a temporary buffer on the stack
I had thought of moving the current functionality of Parrot_allocate into an internal-use-only function (allocate_buffer or some such), which would then be called by both Parrot_allocate and Parrot_reallocate. The alignment/padding rules would then be implemented in _allocate and _reallocate, but nowhere else. Of course, putting the 'correct' buflen into the string header messes up my evil use of the last byte for COWs! -- Peter Gibbs EmKel Systems
