Alan Knowles wrote:
I did start making fixes, but it drove me up the wall, the pointlessness and
stupidity of this change...
Eventually I just disabled E_STRICT in the bootstrap code...
THAT is one of the things that messed me up originally. I had not realised that
one of the libraries was disabling E_STRICT so I wasn't seeing any errors when
I'd switched it back in ...
I think we should allow a free for all on commits to fix this, unless anyone
objects...
Only in so far as it would be nice to have a 'clean' fixing of the problem,
rather than just repairing our own error messages. In this case, I think most of
the core PEAR just needs 'static' adding to each function, but is that all. It
fixes the warnings, but is it the right answer?
--
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
