James G. Sack (jim) wrote:
> Whatever you end up with, I strongly urge minimizing structure,
> especially nesting.
>
> I think the good-ol' ini file format has a LOT of headroom.
> And sections containing tuples map nicely into hashes/dictionaries.
>
> I believe there is a lot of good published code to deal with ini file
> reading and writing.
I like the methods that are used in Postfix. If a line starts with
white space, it's a continuation of the previous line. Commas separate
multi-values on the right side of equality. Default values are
included and commented in the configuration file, so most of the
important values are exposed. If you want to see all the values,
including those not set you can run a command, postconf to see the
values as set. This makes it easier to see them, without the comments
inside the config file. You could do a lot worse, IMNSHO than using a
postfix config file as a model.
Just my $.03, inflation adjusted.
--
Neil Schneider pacneil_at_linuxgeek_dot_net
http://www.paccomp.com
Key fingerprint = 67F0 E493 FCC0 0A8C 769B 8209 32D7 1DB1 8460 C47D
A banker is a fellow who lends you his umbrella when the sun is
shining, but wants it back the minute it begins to rain. - Mark Twain
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
