Re: XML and Config files

Meh, practically any "technology X should never be used for Y" argument of
any significance in IT is simply silly. There are pros and cons to every
sort of configuration file format you can dream up. The reasonable thing to
do is analyze what YOUR particular requirements are and find the best fit
solution to those requirements. There are no hard and fast rules.

INI files are perfectly fine in cases where the structure of the
configuration data is flat, or nearly flat, likely to require hand
customization, and not too excessive in size.

XML is probably a better choice in a variety of situations. Likely reasons
to use XML would be a need to perform complex programmatic manipulations of
the configuration, ensuring a high degree of integrity in the configuration
data, and dealing with complex configurations containing a lot of structured
information.

Personally I think I've used probably just about every shade and variation
of configuration data in programs I've written over the past 27 years. Maybe
not all of those choices were the best possible choice, who knows really,
but I'm not about to start following some one-size-fits-all strategy now...

-- 
The Wise adapts himself to the world. The Fool adapts the world to himself.
Therefore, all progress depends on the Fool.

_______________________________________________
Perl-XML mailing list
[email protected]
To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs