Yes, of course something like this:
/path/to/*Test.php files
/path/to/MyTest.php
Is much better than 1 line in a file that says:
testsuite=/path/to/Test.php
Not to mention the extra K's of code needed to parse that..
:griping: :griping: :roflmao:
I prefer simple (it suits me.. ;-) and tighter code when possible.
Fact is, if things get a bit more complicated, which it more often than not does, maintaining .ini files will become a pain, especially when you made a typo.
I've lost many hours in vain finding some silly typos in linux configuration files. :S
My point was more in the direction of instead of a text editor, using a dedicated configuration editor which makes input easier and let you edit values and metadata seperately as human.
(and a generally available parser as library on the software side)
And considering XML being too resource-hungry, well, it's true. And that's the reason why I actually use JSON, so think JSON instead of XML then for the heck of it.
XML is what everyone knows and understands.
I didn't mention performance issues with XML either because configurations are being read only once during application startup and generally aren't that big to notice the performance hit even on an Amiga 500.
Btw., log files in XML are a VERY bad idea indeed as extensive logging actually CAN slow your application considerably, and make unnecessary big files.
