Re: CVS update: MODIFIED: libsvn_wc ...

Greg Hudson <ghudson@MIT.EDU> writes:

> >> We all agreed that the *correct* solution is to hang a vtable off of
> >> the top-level pool instead of a stream. Whenever a library wants to
> >> send a new kind of feedback to the client app, we can add new vtable
> >> func.
>
> I expect to be overruled here, but: I think this is a recipe for
> spaghetti. Pools are about memory allocation, not feedback.
> Overloading them because they happen to get passed to lots of
> functions is asking for trouble.

So does this mean you're currently unhappy with the fact that our
current exception-handling system (svn_error_t) depends on hanging a
special "error pool" off the top-level pool?

Or are you unhappy that APR even provides the "feature" of associating
arbitrary userdata with a pool?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:31 2006