Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62792
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.223.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <5045FD98.8080306@lsces.co.uk>
References: <AANLkTimWuPXCs-HT6RgQYmH7UKcOYXkeTiMEnBwBXxnt@mail.gmail.com>
 <CAH-PCH4YdBr7WfQ2PR0_Fr_C=TfBsSGsbX3G-jonUqyfLrCcZQ@mail.gmail.com>
 <5040DC47.8000305@ajf.me> <CAH-PCH5TM2ag-5xm3Rk7Ef6LnpEst1UqRoc_f_Uwp_aLe418dA@mail.gmail.com>
 <5040F4D9.80206@sugarcrm.com> <CAEZPtU6X9gLRALzA+KGKNoF5c7ey-xgJ=0NhjF2qVfD9YJqN+Q@mail.gmail.com>
 <5042946A.80204@sugarcrm.com> <op.wjzdwn08idpuyk@damnation.nl.lo.geleia.net>
 <5042A7D6.7050001@lerdorf.com> <op.wjzgbuh1idpuyk@damnation.nl.lo.geleia.net>
 <alpine.DEB.2.02.1209031214250.25835@whisky.home.derickrethans.nl>
 <a565e97fdd574cebf2baca1c54c425a2@nebm.ist.utl.pt> <50452713.3020307@sugarcrm.com>
 <b6bf26cb6b4d2392d5fd13237669a19d@nebm.ist.utl.pt> <5045CAA3.6000409@lsces.co.uk>
 <CAEZPtU77K_wdRErqEQ1ZXj1_sWY2N_UcNkZsL5_h3UfjDmQK1Q@mail.gmail.com>
 <5045E044.9080809@lsces.co.uk> <CAL+t6cHD05znYaq7iPNwFNem=zma0-htbPG-Fc3550U-s5jcRA@mail.gmail.com>
 <5045F939.6010806@lsces.co.uk> <CAEZPtU4POFm-WJBuYj=bWLMqwtHEViVaZ_2XkE5W3CJfg7uPAg@mail.gmail.com>
 <5045FD98.8080306@lsces.co.uk>
Date: Tue, 4 Sep 2012 15:22:13 +0200
Message-ID: <CAEU6NAd3sz2tcZe5gpwkvoRgH3GGQg4BZdPWE9ux3-OZ+zCH5g@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] E_STRICT 'errors' - was Are exceptions allowed in php core?
From: peter.e.lind@gmail.com (Peter Lind)

On 4 September 2012 15:09, Lester Caine <lester@lsces.co.uk> wrote:
> Pierre Joye wrote:
>>
>> On Tue, Sep 4, 2012 at 2:51 PM, Lester Caine<lester@lsces.co.uk>  wrote:
>>
>>> >??? OH YES IT DOES !!!
>>> >MANY times I get a a few lines of text on a white screen ...
>>> >Switch off E_STRICT and everything works fine ... as it was on PHP5.2
>>
>> If you have any doubts about how to configure your development or
>> production servers, how to use logs or how to effectively debug php
>> applications, please ask questions on php-general or php-setup mailing
>> lists.
>>
>> Thanks for your understanding,
>
> Butt out Pierre ...
>
> I keep being told that there is nothing wrong with E_STRICT, and again
> someone has said that it does NOT cause crashes. I beg to differ here - IT
> DOES!
> Now if you are saying that I need to document these crashes as they SHOULD
> not be happening then I'll roll things back and start doing that, but *I*
> thought that these crashes were simply a known effect of using E_STRICT? And
> so I followed the directions, and switched E_STRICT off. On production
> machines of PHP5.3 with E_STRICT enabled and on PHP5.4 one gets white screen
> crashes using older code ... as far as I was concerned that was a known
> fact. Switch it off and everything runs fine!
>

From php.ini:
; display_errors
;   Default Value: On
;   Development Value: On
;   Production Value: Off

In a production environment with display_errors off, E_STRICT doesn't
crash anything. Actually, even with it on, it doesn't crash anything -
shitty code does, by creating notices and then using header() calls
afterwards to create redirects.

Solution: fix your server. Fix your code. It worked for the rest of us.

Regards
Peter

-- 
<hype>
WWW: plphp.dk / plind.dk
CV: careers.stackoverflow.com/peterlind
LinkedIn: plind
Twitter: kafe15
</hype>