Adam Richardson wrote:
I was second-guessing my recall I had a similar issue way back, after
Rasmus pointed out that the custom error handler is called even if
E_STRICT is off. However, I just looked back at my framework code, I
see I'm checking to make sure the error level matches, just as Ferenc
pointed out (what a forgetful old man I am.)
So, I think this could still be causing the issue and it's something
worth exploring on Lester's part.
If I have any custom error handling I don't know about it. I don't think ADOdb
or SMARTY adds anything, and I don't load anything.
Switching back to old code to at least prove to myself I WAS getting crashes, I
got a white screen within half an hour of configuring an old setup. Knowing that
I did get crashes when dealing with 'static' functions, I started there, and now
that other things have been pointed out, the problem in that case is ALL parts
of the codebase need to be updated at once. Otherwise fixing things in one
library breaks other code. It may well be that having got a clean strict PHP5.4
setup I've then been getting problems when porting additional sites over. I KNOW
that I've had a setup where simply switching E_STRICT on and off gives white
screens, and I did have that situation a couple of weeks back. Simply adding and
removing a custom error_reporting() got me working or not, but that was trying
to run Joomla on a PHP5.4 setup with a strict clean PEAR and other libraries. So
I may well have been suffering from 'cross contamination'. But this is the whole
point ... getting a clean setup that will run older sites is a right pain :( I
need to get back to a PHP5.2 setup which works and then cross check what is
failing on the PHP5.4 setup. But none of this is productive work. Nothing I've
moved over in the last 3 months have worked 'out of the box', all have had to
have something done to get them running again. One thing I think is clear is
that I need to avoid using a central PEAR until such time as everything is
stable. Certainly that is this initial crash problem, but I know there were more
problem areas.
I am regretting giving in to the pressure to upgrade the shared codebase to be
strict compliant. I think that I'd much further forward simply ignoring it
altogether and done my own thing. Certainly some third party stuff left is not
going to be work with E_STRICT any time soon :(
--
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
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
