begin quoting Michael O'Keefe as of Fri, Jul 06, 2007 at 04:59:42PM -0700: > Stewart Stremler wrote: [snip] > >Use the right tool for the job, rather than forcing one tool to be used > >everywhere for everything. > > But once you've started using "win.ini" and then get a complicated > structure that you want in the config file, you're at an Oh Shit! > moment. You either hack it up (CSV values, with escapes and all the > parsing that goes with that) or you switch to XML.
Sounds more like you're storing data, rather than configuration. Plus, if your configuration is that complicated, you have another issue: you can no longer configure your program from the command-line. Losing *that* capability bothers me a lot more than XML or no XML. > I find it better to not take the chance and start with XML in the first > place. For config files, I find it better to take the chance and switch. Most of the time, I never have to switch, so all is well. Better a little pain later than a lot of pain now. -- The object of the exercise is to minimize the pain under the curve. Stewart Stremler -- KPLUG-List@kernel-panic.org http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
