[TYPO3-v4] Compatibility break in TYPO3 4.6: need reviews and approval before beta1!
Jigal van Hemert
jigal at xs4all.nl
Fri Jul 15 18:01:51 CEST 2011
Hi,
On 15-7-2011 15:24, Xavier Perseguers wrote:
>>> I think this has also been done for several other classes, so maybe we
>>> should also fix it there. The change was done in commit
>>> eaad40f54eac7d3514223abd2a767099f7790ade.
>>
>> please have a look at the discussion at
>> https://review.typo3.org/#change,1797. Maybe a big notice in NEWS.txt is
>> enough.
>
> Not sure! Hard to believe that someone would stick to PHP4 way of
> instantiating a class but you never know...
A simple Google search already found two extensions which call
parent::tslib_pibase (pp_lib and seminars). Who knows what's in TER and
installations all over the world which calls the old style constructors
(e.g. because they override the constructor)?
>> Otherwise the core rules are clear here and we should deprecate it
>> first, before removing completly.
>
> Somebody willing to have "fun" (:S) with that?
It seems to me that it's part of the '[TASK]' to properly deprecate
functions. Alternative is to revert the change. (Not fixing this would
effectively mean that the deprecation rule can be ignored in the future...)
--
Kind regards / met vriendelijke groet,
Jigal van Hemert.
More information about the TYPO3-project-v4
mailing list