<snip>
Is this change irreversible? Is there anything that can be done to
restore this behaviour? It seems to me that it is a benefit to expect
the log4php ini files behave exactly as the php ini files (or it
should be documented otherwise if they ARE NOT php ini files from
2.2.0 and up).
I'm willing to work on a patch but I wanted to ask first if there is
any consensus about this that I should be aware of.
Hi Marcelo,
Frankly, I did not consider this use case when writing the new parser. You have a valid point, and I'll consider bringing this back as it was. I will first have to consider what else this action might break...
Originally, this is where the idea came from:
To avoid the whole parsing issue, have you considered using the PHP config format? Since 2.2. it is possible to provide it inline as well as in a file.
We're trying to push the PHP and XML formats instead of INI since they're more versatile and easier for us to parse and to document (working on an XSD for next release).
Regards,
Ivan
