svn_io.h and pools

Can I get rid of the pool argument to svn_read_fn_t and
svn_write_fn_t? Basically, if those functions want to do any memory
allocation, they can store an appropriate pool in their batons, and
they have to do that anyway if the memory has to live beyond the
function call. (Since otherwise the output function would have no
idea how long its pool argument is going live and the caller who
passes the pool argument has no idea how long it needs to live.) The
edit_fns interface doesn't pass pools around.

I'm just feeling like it's a little confusing to code read and write
functions and have two different sources of memory pools to allocate
in. Using the wrong one would lead to difficult bugs.
Received on Sat Oct 21 14:36:10 2006