On Fri, June 13, 2008 1:00 pm, Mike Marion wrote:
> I agree with the "XML is the shiznit" thinking too many have. A
> couple years ago at work we had a dba guy that would constantly bring
> up XML in every discussion about everything. From "is your
> configuration in xml? No? You should convert it to XML" to "We should
> store all this info in XML." One of my co-workers (who shall remain
> nameless) wrote out "XML is a fad!" on a paper and tacked it to the
> cube wall of this guy (a bunch of us were in cubes then). Boy was Mr.
> dba mad. We got a chuckle out of that.
>
He deserved worse.
How many config file "standards" have I seen? Far too many, I promise that.
My current practice in Tcl (I recommend it for any scripting language) is
to have a small file of tcl code that's sourced up high. It meets the two
most important criteria I have for configs (neither of which XML provides
as well): Easily human readable and easily language parseable.
Here is an example from my Postgres-Tcl proggies:
[EMAIL PROTECTED] bri_dev]$ cat bri.conf
array set connArray {
host localhost
dbname scm
port 5432
user barnesl
}
--
Lan Barnes
SCM Analyst Linux Guy
Tcl/Tk Enthusiast Biodiesel Brewer
--
KPLUG-List@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
