nico wrote:
I see, but in my opinion since the recover mode is off by default and
E_WARNING is on by default, if recover mode is explicitly activated
php should respect the developer's need to keep the interpreter as
quiet as possible.
A developer with more stringent needs will either keep recover mode off
or activate it alongside with E_WARNING.
If someone actually has a reason to use recover mode, then they probably
would be using libxml_use_internal_errors(TRUE) as well.
It is painful (maybe not enough) to use recover mode for a reason.
BTW, I've seen thousand of xml docs declared "broken" not for syntax
errors, but
for the simple presence of characters not corresponding the the
encoding specified...
And that somehow makes it any better than having syntax errors?
Rob
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
