[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

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

From: Sean Russell <ser_at_germane-software.com>
Date: 2002-03-13 00:32:28 CET

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 12 March 2002 14:19, you wrote:
> > 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?"

I'll admit that I haven't seen this posting, but I am reminded of Apache's
history. It seems to me that, in the early days, there was a single big
config file. Then there was a profusion of separate config files, which were
all eventually merged back in to the main config file -- I assumed because it
was more confusing to have multiple config files.

Eventually, a complex Apache configuration will tend to be broken out into
multiple 'include'd files, but initially, everything starts out in one file.
I don't know enough about the Subversion architecture to say whether this is
a model that should be followed, but it seems to me to be a similar situation
in which all of the work of deciding which way is better has already been
done.

> > > 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 :-)

Again, I'm probably way off base, but are you familiar with PYX? PYX is a
highly simplified version of XML. It maintains document structure, but is
easily parsed with standard *nix command-line tools. I've found it to be
ideally suited for configuration files, and use it because PYX parsers are
nearly trivial to write and are extremely small... perfect for small
applications where XML is too heavy. For that matter, since Subversion
contains an XML parser, is there a reason to not use an XML based config
file, making it similar to Apache's?

I'm sure this has all been discussed before, and XML was thrown out for a very
good reason; if so, redirect this email to /dev/null.

- --- SER
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8jpAUURPYGmmGtGcRAsWYAJ9BTn3D7AAuclsnLONED00FKgXJ5gCfYrRS
YpVMiKLjL+GSBIUre1fwY6I=
=uUXS
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Mar 13 00:33:27 2002

This is an archived mail posted to the Subversion Dev mailing list.