> Why add new functions instead of patching the current ones?
I didn't know if the original functions still had a purpose. Perhaps you would want to Parrot_allocate for something non-bufferish? Thinking about it, that seems evilly wrong, so I guess that is not a valid reason. Doing 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 to call the function, or stash away the values of the incoming buffer before it gets overwritten, so it can later memcpy. Should I resubmit a patch removing the _buffer suffix, and removing mem_realloc? Thanks, Mike Lambert
