[TYPO3-core] 6.2-git: compatibility with 4.x

[Patrick Schriner]

I'd favor removing it as planned.

If it's not removed you could have web sites running 6.2 LTS in 3+ years  
having the very same migration problem they'd have next year.

If you remove it: Yes it might hurt when moving to 6.2, but you have can  
reasonably assume your efforts will not be in vain.

Autoloader files can be generated almost for free with extdeveval - if  
it's working.

I think it's fair to assume that given there is > 1+ year grace period  
between 6.2 LTS release and 4.5 LTS end of maintenance will suffice to  
bring old extensions up to speed.

Maybe a semi-official patch repository for old extensions would be better  
to share patches?

Patrick

On Wed, 05 Jun 2013 12:19:45 +0200, Michael Stucki  
<michael.stucki at typo3.org> wrote:

> Just noticed this thread. I wonder, does it make any sense to remove a
> compatibility layer right now?
>
> How about waiting and removing it after the LTS?
>
> - michael
>
> Am 31.05.2013 14:17, schrieb Jigal van Hemert:
>> Hi,
>>
>> On 31-5-2013 12:38, Christian Weiske wrote:
>>>> What "compatibility layer" do you mean? Class names without the
>>>> namespace changes can still be used.
>>>> What functionality seems to be missing for you?
>>>
>>> The directory and its contents
>>>> typo3/sysext/cms/tslib/interfaces/
>>> is missing in typo3 core master currently. It exists in 4.5 and 4.7
>>> and 6.1.
>>
>> Correct. Those files were deprecated in 6.0 and scheduled to be removed
>> in 6.2 (as shown in each of those files in 6.0 and 6.1).
>> They were only useful for explicit require/include statements. These
>> explicit includes can not be used in 6.2; your code must rely on the
>> autoloader (that is already working since 4.3 if I remember correctly)
>> and extensions must proved an ext_autoload.php file for the autoloader
>> (if they can't be loaded by convention).
>>
>


-- 
Patrick Schriner