Hi!
Now that we've decided to add E_STRICT to E_ALL error mask, the question
is - what should we put in recommended production INI - should we
include E_STRICT or not?
Development has E_STRICT anyway, so no question there.
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227
Now that we've decided to add
E_STRICTtoE_ALLerror mask, the question
is - what should we put in recommended production INI - should we include
E_STRICTor not?
Development hasE_STRICTanyway, so no question there.
I can't look it up easily at the moment, but assuming display_errors is off
on the production configuration, I'd be inclined to make the error_reporting
levels the same: that is, include E_STRICT.
Adam
Hi!
Now that we've decided to add
E_STRICTtoE_ALLerror mask, the question is
- what should we put in recommended production INI - should we include
E_STRICTor not?
Development hasE_STRICTanyway, so no question there.
I think no.
first of all, 1 think it would be better to change only one thing at a
time (add E_STRICT to E_ALL), and we also exclude E_DEPRECATED for
production, which would imo much more important for most apps than
fixing the E_STRICT problems.
--
Ferenc Kovács
@Tyr43l - http://tyrael.hu
Hi Folks:
first of all, 1 think it would be better to change only one thing at a
time (addE_STRICTto E_ALL), and we also excludeE_DEPRECATEDfor
production, which would imo much more important for most apps than
fixing theE_STRICTproblems.
I'm thinking similarly. Strict is totaly unimportant in production.
Deprecated warnings, on the other hand, can be helpful in production.
We all have some bits of code that only gets reached in unusual
circumstances. Those situations often only arise in production.
Getting told about them can be a good thing.
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
hi Stas,
The idea of E_STRICT when we introduced it was to help developers. So
I tend to think that we should not enable it in php.ini-production.
Hi!
Now that we've decided to add
E_STRICTtoE_ALLerror mask, the question is
- what should we put in recommended production INI - should we include
E_STRICTor not?
Development hasE_STRICTanyway, so no question there.
--
Stanislav Malyshev, Software Architect
SugarCRM: http://www.sugarcrm.com/
(408)454-6900 ext. 227--
--
Pierre
@pierrejoye | http://blog.thepimp.net | http://www.libgd.org
2011/7/23 Pierre Joye pierre.php@gmail.com:
hi Stas,
The idea of
E_STRICTwhen we introduced it was to help developers. So
I tend to think that we should not enable it in php.ini-production.
Agreed.
--
Regards,
Felipe Pena
-----Original Message-----
From: Pierre Joye [mailto:pierre.php@gmail.com]
Sent: Saturday, July 23, 2011 3:22 PM
To: Stas Malyshev
Cc: PHP Internals
Subject: Re: [PHP-DEV]E_STRICTin productionhi Stas,
The idea of
E_STRICTwhen we introduced it was to help developers. So I
tend to think that we should not enable it in php.ini-production.
Agree.
Andi