Re: Context parameter in public API

Nuutti Kotivuori <naked@iki.fi> writes:
> Is the 'config' file a feature of svn_client libraries or is it
> something that only the command-line client uses?

It's a feature of all of clients, IMHO. Our other configuration files
(proxies) affect all clients, no reason why this one shouldn't as
well. There might eventually be configuration options which are
specific to certain clients, but we can deal with that when it arises.

> If it is a part of the svn_client library functionality - then it
> sprouts a few more questions. Is svn_time_to_human_nts part of the
> svn_client library? I guess it is since it's supposed to be called by
> the callers of svn_client library. Does that mean that if the context
> is implemented, you cannot call svn_time_to_human_nts without having a
> context? How does this affect svnadmin and svnlook which need it too?

Hmmm. I mean, we could define svn_time_to_human_nts's behavior when
the context baton is null, that's one solution.

Or, instead of a context baton, should we just have a global
Configuration object? (Please, no reflexive "globals are evil"
responses. If this particular use of a global object is evil, say
exactly why.)

> So, I am a bit of a loss here - this is your territory, not mine :-)

I guess I'll need to work on expanding your territory to include all
of Subversion, then :-).

(Heh, not trying to avoid the discussion, just saying that you don't
need to limit your scope in Subversion.)

-K

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Oct 11 18:44:18 2002