Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:62795
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.184 cause and error)
Message-ID: <504605A5.3000600@lsces.co.uk>
Date: Tue, 04 Sep 2012 14:44:05 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120604 Firefox/13.0 SeaMonkey/2.10
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <AANLkTimWuPXCs-HT6RgQYmH7UKcOYXkeTiMEnBwBXxnt@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> <CAEU6NAd3sz2tcZe5gpwkvoRgH3GGQg4BZdPWE9ux3-OZ+zCH5g@mail.gmail.com>
In-Reply-To: <CAEU6NAd3sz2tcZe5gpwkvoRgH3GGQg4BZdPWE9ux3-OZ+zCH5g@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] E_STRICT 'errors' - was Are exceptions allowed in php
 core?
From: lester@lsces.co.uk (Lester Caine)

Peter Lind wrote:
>>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.

Using third party code - joomla - only difference between working and not 
working is switching E_STRICT on. With display_errors=off one gets a white 
screen. I was not surprised as I've had this all the way through with code from 
many sources. Yes a lot of the time you just get the error messages, but a white 
screen crash has been the norm most of the time so leaving display_errors=on 
helps while fault finding on the development systems.

Most of the production strict fixes have now been committed on my own code, but 
I think I've still got an older 5.2 machine that still has the earlier code. I 
THINK one of the crashes comes when using $this in a static function. Certainly 
a lot of the recoding has been splitting a lot of these out to two separate 
functions but I've been seeing white screens for the past year as I work through 
third part code and to be honest since ALL I was changing as E_STRICT I had not 
looked much closer :( Other than e_strict and fatal as the last message visible.

-- 
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk