Re: PEAR Coding Standards

I would much rather have a PEAR class return a PEAR_Error when there is a problem, than have PHP throw an error. Isn't this the entire reason for having an error handling class any way? To allow the programmer to decided how to handle errors? On May 3, 2004, at 7:27 AM, Thorsten Suckow-Homberg wrote:

If you are ever going to update the PEAR Coding Standards, here are my suggestions which should find their way into the doc IMHO: a) Use error_reporting(E_ALL) while developing your PEAR Package b) You are not allowed to use the "@" for hiding error-messages in any way. Just my 2 cents. -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php