Context parameter in public API

brane@xbc.nu wrote:
> We're fairly screwed by not having a context parameter in the public
> API. That means we can't pass configuration data down the call
> chain, among other things (such a beast would be ideal for
> cancellation processing, too...).

Right.

> We're reading and parsing the config files multiple times already,
> which is bad.

Agreed.

> So, how about adding a context parameter to every function? I know
> that's a big change, but I think we'll be forced to do that sooner
> or later anyway.

Er um er. My knees are already shaking. Every function? :-)

I think someone more knowledgeable than me should define a bit more
carefully what indeed is 'every' function - and how the whole thing
should be handled.

In the meantime, I think I'll go do something else :-)

-- Naked

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Oct 6 18:58:07 2002