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... I think we should allow a free for all on commits to fix this, unless anyone objects... Regards Alan -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. Lester Caine <les...@lsces.co.uk> wrote: I know I'll be kicked somewhere else, but I think it's important that the general community appreciates what is going on ... I've cleared the bulk of the 'strict' warnings on bitweaver, and in the libraries, but now I'm down to PEAR ... is there a version of PEAR that is strict compliant? I've certainly not found anything and now I'm having to work through that to remove the next layer of warnings! So is anybody else working on the same problem? -- 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 -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
