[TYPO3-core] Second Meeting for TYPO3 6.2 LTS Release

Helmut Hummel helmut.hummel at typo3.org
Mon May 27 09:24:12 CEST 2013

On 25.05.13 20:16, Ernesto Baschny wrote:
> Hi,
> read more about what's going on "behind the scenes" of the TYPO3 6.2
> Release here:
> http://forge.typo3.org/news/643

One thing I want to calrify. Is it really the intention to re-introduce 
int_from_ver into GeneralUtility like so: https://review.typo3.org/21047 ?

I think this would cause even more confusion which API to use.
"Old" extensions used t3lib_div::int_from_ver, then had to use 

With 6.0 t3lib_utility_VersionNumber was aliased to 
\TYPO3\CMS\Core\Utility\VersionNumberUtility and t3lib_div to 

This means in 6.0 you could use:



All doing the same.

But I assume nobody used GeneralUtility::int_from_ver() as this would 
only work in 6.0 and writes deprecation messages, so it does not make 
sense to do so.

In 6.1


has been removed, breaking "old" extensions.

As much as I see the need to not break extensions during a migration 
from 4.5 to 6.2, I don't like to introduce 
GeneralUtility::int_from_ver() again, but instead an (optional) 
compatibility layer which provides this (and potentially other) 
method(s) to t3lib_div using inheritance instead of aliasing.

Find a rough prototype in my sandbox[1]

There is a chicken/egg problem however, as I would like to have the 
t3lib_div alias in place early in the boot process if the compatibility 
extension is not installed. At this stage, it is however not (yet) 
possible to know if the extension is installed or not.

Nevertheless I think it is worth solving this problem instead of 
bringing back in_from_ver() to GeneralUtility as by that we virtually 
never can get rid of it.

Kind regards,

[1]git cherry-pick origin/sandbox/helhum/t3lib_div-compatibility

Helmut Hummel
Release Manager TYPO3 6.0
TYPO3 Core Developer, TYPO3 Security Team Member

TYPO3 .... inspiring people to share!
Get involved: typo3.org

More information about the TYPO3-team-core mailing list