On Wed, 2015-04-08 at 10:48 -0400, Alan Conway wrote: > ... > The issue is that we need buffer growth AND control over allocation. > pn_buffer_t forces use of malloc/free/realloc. That won't help if you're > trying to get the data into a buffer allocated by Go for example. I > agree a growable buffer type is a nicer API than raw function pointers, > but the buffer type itself would need to use function pointers so we can > replace the functions used for alloc/free/realloc.
I think this is a pretty general issue actually that also crops up in embedded systems, where you want some different control over memory allocation. I think it might be better addressed by making malloc/free/realloc replaceable for the whole of proton - would that solve your go issue? Andrew
