Ferenc Kovacs wrote:
some/most of the E_STRICT messages are telling you about (possible) problems in
your code.
The major hurdle here is 'static', and not being able to use a function both
statically or with $this. PEAR is currently throwing these 'warnings' so is
there problems in the PEAR code!
you can decide to ignore them, but imo it is a good thing that we tell those to
the developer.
The 5.3 stance was 'just switch them off'. With 5.4 changing the rules again,
the 5.3 stance was no longer tenable so we had to rework all the code which is
now at the fix PEAR stage! So currently 'E_STATIC' has to be switched off still
since you can't have all the message being generated.
the PHP4->PHP5 transition was pretty major, I'm surprised that your "php5 code"
worked on php4 just fine.
As I have said before and will continue to say. I never USED PHP4, but all of
the projects I contribute to ran as clean on PHP4 as they did on PHP5.0 and 5.1.
PHP5.2 introduced the first major break, and was the first time we had to worry
about a 'transition' ... I don't recognise 4to5 being major as long as you kept
the PHP5 stuff that was being used tidy. I would have preferred that PHP5.3 had
simply been called PHP6 and then a PHP5.2 branch maintained for security
upgrades then I don't think I'd be having nearly as much trouble these days. I
currently have sites down simply because something is not set right, and I can't
find the pigging problem. Not just PHP, but also Apache ... Fortunately the
PHP5.2 systems have not been taken down yet.
--
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
