I'd have to agree with the people who've suggested using XML. Using XML
simplifies learning the syntax and makes it easier to write tools for
editing the config files that won't conflict with hand-editing the config
files. If some people want to dynamiclly generate portions of the config
file (rather than all at once prior to reading the file) then I'd go with
some sort of tag that specifies the path to that program. Then if I want
to write a section in Java, one in PHP, one in Python, one in TCL, and one
in a shell script I can without messing up my nice-neat XML config
file. Possibly could even allow inline code in cases where we're using a
scripting language and not calling a binary.


Reply via email to