comma vs space (was: Re: supporting http proxy via a config file)

On Tue, Mar 12, 2002 at 01:49:08PM -0600, Karl Fogel wrote:
> Greg Stein <gstein@lyra.org> writes:
>...
> Hmmm, yeah, this is a specific instance of the general question: do we
> want separate files under .subversion/ for different kinds of
> configurations, or do we want a single .subversion/config with lots of
> sections? (Either way, every config file supports sections, of
> course.)
>
> It seems like a bikeshed to me, I confess, but maybe there's a
> convincing argument for why one way is better. Anyone care?

See my recent note titled "single or multiple configs?"

> > For the [default] case above, it is also important to have a way to disable
> > the default proxy. For example:
> >
> > no_proxy = *.collab.net, *.webdav.org
> >
> > (yes, the pattern ought to be comma-separated globs...)
>
> Why comma-separated, not space-separated?

I think there will be other cases where you have "lists" of data. So the
question comes up: which will be more common in values? commas or spaces? If
you say commas are common, so use spaces, then I'd like to see the data that
has a comma without a following space :-)

The net result is that you have a standard "list format" for option values.
That is: comma-separated values.

Note that we should create: svn_string_split() which takes an svn_string_t,
a separator, and a flag on whether to strip leading/trailing whitespace.
That function could be used to split paths, split log messages, split
svn:ignore properties, and split comma-separated lists.

Cheers,
-g

-- 
Greg Stein, http://www.lyra.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org