# strict compliance ... - Thread: https://externals.io/message/61748 - Original archive: https://news-web.php.net/php.internals/61748 - Started by Lester Caine on 2012-07-25T09:02:03+00:00 - Messages: 3 - Reply by email to internals@lists.php.net - More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt --- ## #61748 — Lester Caine — 2012-07-25T09:02:03+00:00 URL: https://externals.io/message/61748#61748 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 --- ## #61829 — Alan Knowles — 2012-07-25T11:56:52+00:00 URL: https://externals.io/message/61748#61829 · In reply to: #61748 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 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 -- -- Sent from my Android phone with K-9 Mail. Please excuse my brevity. --- ## #61761 — Lester Caine — 2012-07-25T14:06:17+00:00 URL: https://externals.io/message/61748#61761 · In reply to: #61829 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