Re: E_STRICT 'errors' - was Are exceptions allowed in php core?

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