.. and everybody just needs to lift the finger to turn the wheel that little bit to prevent hitting the wall.
Anyways I just posted the following email to internals in a list attempt to get some of the people with php-dev karma to lift their finger:
Hi,
I just want to say once again that all hell is going to break loose once we release 5.2.0 as stable thanks to the various fatal errors we are adding for perfectly working code that breaks OO theory.
I am talking about this change:
http://marc.theaimsgroup.com/?l=php-dev&m=114734977430980&w=2
As well as the rewriting signatures when inheriting and whatever other fatal errors we are adding to things that are not actually fatal. Please for the love of PHP, make these E_STRICT or E_NOTICE. Otherwise we will have an army of angry users that will dwarf the one we were facing with PHP 4.4.
Now is the time to fix this before RC6.
regards,
Lukas
Things like the 5.2.0 issues you mention, amateurish API design (why did it take until 5.1.3 for simplexml to acquire getName()?), release bungling (5.1.3 especially), and bug 38996 are building too much negative karma around PHP for my company. We will be seriously considering everything but PHP for our next project: Perl, Python, and even Lisp (!).
only a braindead developer would set a static method abstract. using static methods for oo design is just silly/useless.
but you're right, this change should not happen in minor versions :)
This is not good at all !
sapphirecat you get what you pay for...
Oh wait...
Well it seems like in the end Ilia went ahead and made sure that all these new fatal errors were reduced to much more manageable strict notices. Also it was decided to split off deprecation from the rest of the strict notices. This will make it much easier to enable strict notices in development of code that is to work across multiple different minor versions.