Re: handling errors

You are completely right. Do intensive error checking. In thousands and thousands of lines of code, I think i only used @ in 3 places - in the functions that connect to the database - I have more robust error checking in place. -Jason Garber deltacron.com At 09:26 AM 9/27/2001 +0200, * R&zE: wrote:

<Original message> From: Jason G. <blair@nb.net> Date: Thu, Sep 27, 2001 at 03:25:16AM -0400 Message-ID: <5.1.0.14.0.20010927032422.0797b078@pop3.nb.net> Subject: Re: [PHP] handling errors Placing an @ symbol before the function name will suppress any errors. @GetImageSize() </Original message> <Reply> Yep, I know it does. Yet, it's still no good way of handling your errors/warnings. Unless you made some real intensive errorchecking yourself, you should not use that @-construction or lower the errorreportinglevel. Reporting should be as high as possible (E_ALL). And yes, indeed, it might then just be that you get a lot of warnings (and/or errors). Then you have to fix your code, not start using @ in order to supress them. Errors and warnings are not reported without a reason you know. Even if your code works, when there are warnings it can still happen that in some situation the code will crash. </Reply> -- * R&zE: -- »»»»»»»»»»»»»»»»»»»»»»»» -- Renze Munnik -- DataLink BV -- -- E: renze@datalink.nl -- W: +31 23 5326162 -- F: +31 23 5322144 -- M: +31 6 21811143 -- -- Stationsplein 82 -- 2011 LM HAARLEM -- Netherlands -- -- http://www.datalink.nl -- «««««««««««««««««««««««« -- PHP General Mailing List (http://www.php.net/) To unsubscribe, e-mail: php-general-unsubscribe@lists.php.net For additional commands, e-mail: php-general-help@lists.php.net To contact the list administrators, e-mail: php-list-admin@lists.php.net