On Tue, 8 May 2007, Ilia Alshanetsky wrote: > It is better because it won't show up on most systems. As far as taking out > the error message entirely, that is not a good idea because that takes away > your ability to determine what went wrong in parsing of the file.
But the only way of figuring it out now and presenting the result to the user is by parsing an error message that you get by catching the message in php_lasterrmsg() - which is *ugly* to say at least as it means you'd have to use @ to silence this call as well, in case you run with E_ALL (on development servers). However, using @ makes you hide perhaps fatal errors. So I think having any warning here is a pain. Derick -- PHP CVS Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
