Re: PHP 4.0 Bug #8294 Updated: Documented behavior of @ operator does not match actual behavior

From: Date: Sat, 16 Dec 2000 22:32:34 +0000
Subject: Re: PHP 4.0 Bug #8294 Updated: Documented behavior of @ operator does not match actual behavior
References: 1  Groups: php.dev 
Request: Send a blank email to php-dev+get-41623@lists.php.net to get a copy of this message
I did not state that the behavior of the operator was was a problem. :) I stated that the documentation does not match how the operator behaves. I also noted that I thought that the current behavior made sense... Is this not clear? --zak ----- Original Message ----- From: <waldschrott@php.net> To: <php-dev@lists.php.net> Sent: Saturday, December 16, 2000 12:11 PM Subject: [PHP-DEV] PHP 4.0 Bug #8294 Updated: Documented behavior of @ operator does not match actual behavior > ID: 8294 > Updated by: waldschrott > Reported By: zak@php.net > Status: Open > Bug Type: Documentation problem > Assigned To: > Comments: > > I do not think this is a problem, why suppress a fatal error > if your script will break at this point at any rate? use > error_reporting() then (for productional sites) > > the only thing which should be documented (if not already > done) it that errors from statements will not be suppressed > > Previous Comments: > -------------------------------------------------------------------------- - > > [2000-12-16 12:11:30] zak@php.net > The documentation states that the @ operator suppresses all errors. > > However, lines like: > @ error_reporting E_ALL); > still generate parse errors. > > I think that the current behavior is the right thing to do - AFAIK, there is no way to induce a parse error at runtime. Parse errors in the code that makes up the arguments for eval() and create_function() are caught and handled differently then normal parse errors (at least AFAICT they are - @ suppresses the errors generated in this fashion). > > The only real case that I can think of where you might have parse errors at runtime would be situations where you are dynamically including code from untested files -- if you are doing that though, then catching parse errors is probably the least of your worries. :) > > -------------------------------------------------------------------------- - > > > Full Bug description available at: http://bugs.php.net/?id=8294 > > > -- > 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 >

« previous php.dev (#41623) next »