hi,
A small reminder about what we may not do :)
It would rock if we don't introduce behaviors changes in 5.2 anymore
as it is really meant for security fixes only. The last in date is
breaking something that was working for the last ten 5.2 releases:
http://bugs.php.net/bug.php?id=44144
It could be seen as logical and harmless but it can have dramatic side
effects, especially for something as critical than autoload.
Cheers,
Pierre
hi,
A small reminder about what we may not do :)
It would rock if we don't introduce behaviors changes in 5.2 anymore
as it is really meant for security fixes only. The last in date is
I find it very hard to believe that "over 75 bug fixes" were all
security related
breaking something that was working for the last ten 5.2 releases:
http://bugs.php.net/bug.php?id=44144
It could be seen as logical and harmless but it can have dramatic side
effects, especially for something as critical than autoload.
Fortunately, making it very obvious to see your application is failing
as it doesn't work at all. It however isn't in the autoloader. Its in
a function that returns all SPL autoloaders.
And a fun fact: Is barely documented. Just like ~50% of the rest of
the SPL stuff.
This is a pure bugfix which was fixed over 2 years ago. Thats quite
some time to wait for an obvious bugfix.
If people had workaround for this bug (I'm not sure how that is
actually possible, as the returned value made no sense and you have no
chance of getting the real object back) then they would have
implemented the expected behavior too, hence not breaking anything.
And. It was not considered as BC break according to the 5.3 release
notes. Just a good old bugfix.
Its also a bit funny that a guy from symfony reported that ticket,
especially since it was a symfony guy who reported that bug to me...
-Hannes