[TYPO3-dev] Extensions need update for 4.3!

Martin Kutschker masi-no at spam-typo3.org
Fri Oct 10 08:58:32 CEST 2008


Xavier Perseguers schrieb:
> Hi all,
> 
>>>> There are some changes that are of course not backwards compatible,
>>>> which will break extensions and which we did in the past (upgrade to
>>>> PHP5, change of paths and symlinks), but in most case there was a good
>>>> reason to do so, breaking the one or other existing extensions. In my
>>>> eyes this is not a good reason.
>>
>>> Broken extension can be easily fixed by changing null to a proper
>>> argument. Why are you resisting it? Why does it look good to you to pass
>>> wrong arguments to functions?
>>
>> Well, NULL wasn't wrong until probably 4.3, those extensions were not
>> "broken" before, which is why I don't think they should "brake" after
>> the 4.3 upgrade.
> 
> I think there is a solution for all of us... allowing NULL to be passed
> in 4.3 but somehow declare this deprecated, which would then
> "officially" let us remove this behaviour in AFAIK 4.5.
> 
> What do you think of that?

Nothing. It's time that the TYPO3 and the TYPO3 extensions "grow up" and
behave like a it's supposed from real programming languages and honour
variable types.

Masi




More information about the TYPO3-dev mailing list