Hi Folks:
On Sun, Jul 24, 2011 at 12:18:51AM +0200, Ferenc Kovacs wrote:
>
> 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 th
>-Original Message-
>From: Pierre Joye [mailto:pierre@gmail.com]
>Sent: Saturday, July 23, 2011 3:22 PM
>To: Stas Malyshev
>Cc: PHP Internals
>Subject: Re: [PHP-DEV] E_STRICT in production
>
>hi Stas,
>
>The idea of E_STRICT when we introduced it was to
2011/7/23 Pierre Joye :
> 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.
>
Agreed.
--
Regards,
Felipe Pena
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: ht
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.
On Sat, Jul 23, 2011 at 11:50 PM, Stas Malyshev wrote:
> Hi!
>
> Now that we've decided to add E_STRICT to E_ALL error mask, the question is
> - what
On Sat, Jul 23, 2011 at 11:50 PM, Stas Malyshev wrote:
> 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.
I think
On Jul 23, 2011 2:51 PM, "Stas Malyshev" wrote:
> 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.
I can't look it up easily
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
