From: Ciaran McCreesh <ciaranm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: gcc-config 2.0 development
Date: Tue, 9 Aug 2005 23:28:08 +0100 [thread overview]
Message-ID: <20050809232808.0ae0de2a@snowdrop.home> (raw)
In-Reply-To: <1123625568.11092.30.camel@cloud.outersquare.org>
[-- Attachment #1: Type: text/plain, Size: 1985 bytes --]
On Tue, 09 Aug 2005 15:12:48 -0700 Jeremy Huddleston
<eradicator@gentoo.org> wrote:
| On Tue, 2005-08-09 at 22:19 +0100, Ciaran McCreesh wrote:
| > | but I think having the xml configuration files allows a much more
| > | robust configuration.
| >
| > How so? Using XML doesn't magically make your data files any
| > different. It simply makes them much harder to parse.
|
| That's a matter of opinion.
Not really. It's pretty easy to prove that a full XML parser is
computationally more complicated (and hence slower and more bug prone)
than most 'obvious' flat text file formats.
| I see it as a way to abstract away the
| configuration and utilize an existing library to handle the parsing.
| If we do want to eliminate outside dependencies (which I think is an
| extremely valid point and concern), then we could internally
| implement a different configuration format that is easier to parse.
Interacting with an XML library is around the same degree of difficulty
as writing a simple flat text parser. Remember that if you're using
XML, you have to be able to handle *all* the fancy XML nonsense,
including DTD voodoo and processor directives.
The only 'advantages' to XML are that you can partially validate the
syntax (but not the contents) of a file and that by writing a really
complicated XSLT mess you can transform it into a different XML file.
The former is a duff argument because a) the only reason you need
validation is because XML's syntax is so complicated and b) you can't
validate CDATA things anyway. The latter is silly because you can use
sed, grep, cut etc on any sane textfile format, and it's far easier
than XSLT.
| I'd probably go for something similar to the samba/gdm config files
| if we were to go down this road:
<snip>
Much saner.
--
Ciaran McCreesh : Gentoo Developer (Vim, Shell tools, Fluxbox, Cron)
Mail : ciaranm at gentoo.org
Web : http://dev.gentoo.org/~ciaranm
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-08-09 22:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-09 20:53 [gentoo-dev] gcc-config 2.0 development Jeremy Huddleston
2005-08-09 21:19 ` Ciaran McCreesh
2005-08-09 22:12 ` [gentoo-dev] " Jeremy Huddleston
2005-08-09 22:14 ` Daniel Ostrow
2005-08-09 22:37 ` Paul Varner
2005-08-09 22:43 ` Mike Frysinger
2005-08-09 22:50 ` Ciaran McCreesh
2005-08-09 22:53 ` Diego 'Flameeyes' Pettenò
2005-08-09 22:28 ` Ciaran McCreesh [this message]
2005-08-09 22:34 ` Diego 'Flameeyes' Pettenò
2005-08-09 23:48 ` Jeremy Huddleston
2005-08-09 22:47 ` Ferris McCormick
2005-08-10 1:08 ` [gentoo-dev] " Donnie Berkholz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050809232808.0ae0de2a@snowdrop.home \
--to=ciaranm@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox