Title: RE: curious: why an xml config file?
Thread: curious: why an xml config file?
Forum: Need Help?
Conference: ColdBox
User: ziggy
--Hard-coding the data
XML is hard coded data as well. Anyway, in your
address example, you'd have to modify the xml data with every change too. No
difference.
Often is zealotry, rather than clear evaluation of functionality.
How many people have ever been able to reuse a framework config.xml without any
editing, and how often? The fact that you have to take special steps to hide an
xml config file which offers no benefits in itself, alongside switching to a 2nd
language, and parsing it, is enough to tell me a standard one is better.
Not
that it matters much for one file, just have never received a good answer from
anyone about real-world benefits - except Luis answer of one actual benefit to
him:
"its for ease of use in representing data much cleaner than structures."