On Wednesday 03 April 2002 05:35, Michel J Lambert wrote: > > My first thoughts on this are that we should go the whole way, and have > > Parrot_allocate take a Buffer* and a requested size, and let it fill in the > > bufstart and buflen parameters (as in the not-yet-implemented > > Parrot_reallocate patch). > > Heh, I thought the exact same thing when I first saw your realloc patch. > Below is a cvs-relative patch (meaning it 'includes' Peter's patch > as well, since it is unapplied), that builds off of his Parrot_reallocate > to rename it to be Parrot_reallocate_buffer and adds a new function, > Parrot_allocate_buffer. I did this over the weekend, but this looks like > an opportune time to submit it. :) This patch also cleans up parrot code > to use the defined memory interface in memory.c and resources.c > (mem_sys_realloc versus realloc, etc).
Why add new functions instead of patching the current ones? -- Bryan C. Warnock [EMAIL PROTECTED]
