Re: PHP 4.0 Bug #5601: @function() should not turn oferror reporting for critical errors

From: Date: Fri, 14 Jul 2000 14:52:39 +0000
Subject: Re: PHP 4.0 Bug #5601: @function() should not turn oferror reporting for critical errors
References: 1 2  Groups: php.dev 
Request: Send a blank email to php-dev+get-24536@lists.php.net to get a copy of this message
On Fri, Jul 14, 2000 at 04:24:35PM +0200, Hartmut Holzgraefe wrote: > Rasmus Lerdorf wrote: > > > > The whole point of @ is to swallow those errors and not expose them to the > > remote user. If you are using @ you are basically telling PHP you will > > check the errors yourself. > > yes, but on certain errors, especially "undefined function", > PHP will terminate execution so that i get no chance to > check for the error myself > > and finding an error in a script that doesn't return anything > ("document contains no data" and no error message at all) > is no fun, at least as long as there's no debugger beyond > the level of printf ... i have to agree to hartmut here - i think all errors that will terminate the execution should be at least logged. tc > > > -- > Hartmut Holzgraefe > hartmut@six.de http://www.six.de +49-711-99091-62 > fax:-99 > > -- > PHP Development Mailing List <http://www.php.net/> > To unsubscribe, e-mail: php-dev-unsubscribe@lists.php.net > For additional commands, e-mail: php-dev-help@lists.php.net > To contact the list administrators, e-mail: php-list-admin@lists.php.net -- Thies C. Arntzen "One Big-Mac, Small Fries and a Coke!" Digital Collections Phone +49 40 235350 Fax +49 40 23535180 Hammerbrookstr. 93 20097 Hamburg / Germany

« previous php.dev (#24536) next »