Hey Stas:
On Mon, Aug 24, 2009 at 11:43:22PM -0700, Stanislav Malyshev wrote:
>
> That's true. So, if you use code that uses $php_errormsg, of course you
> can not use this optimization and should not enable it (at least for
> error types and code parts that you use $php_errormsg with).
Exactly. Totally killing E_STRICT on it's own seems like the biggest win
(in the right circumstances).
My main point is that we need to think this thing through carefully and
document it well.
> Also, if you use @ to stop warning output to the browser you should read
> the manual about display_errors and part of the security guidelines when
> it says never enable display_errors in production ;)
Of course. But folks don't want those same messages showing up in the
error log, either.
Thanks,
--Dan
--
T H E A N A L Y S I S A N D S O L U T I O N S C O M P A N Y
data intensive web and database programming
http://www.AnalysisAndSolutions.com/
4015 7th Ave #4, Brooklyn NY 11232 v: 718-854-0335 f: 718-854-0409
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
