[TYPO3-core] Minutes of the 6.0 release team meeting

[Thomas Maroschik]

Hi Philipp,

> It does autoload the classes, but nothing else.
> As this is a build-in function, it should be really fast, because both names
> reference the same class.
> Looking at the PHP source confirms, that the class is autoloaded and the
> alias is added to the class look up hash map. So it just uses up a few CPU
> cycles to create a new entry in the list of classes to point to the existing
> class.

Thanks for the research.

> Or a source code update script like for FLOW3.

I hope the FLOW3 Team will include my refactoring tool in their code 
migrations wizards. Currently they're doing plain regex search. The 
refactorer builds a custom AST by the PHPParser from Nikita Popov. This 
means it's pretty safe to apply it, as the semantics of the language are 
kept. You know, don't parse HTML with Regex ;)

I'm working on a compiler for FLOW3 CLI tools, that spits out a single 
Phar, so that such utilities can be used without setting up a whole 
FLOW3 instance.

> I am still in favor of separate extension repositories for the two major
> branches anyway.
> But independent of that, the whole point of the alias stuff is to provide
> backwards compatibility.
> If the performance penalty is not too bad, we can leave the compatibility
> layer in the whole v6 branch and only remove it together with v7.

I already thought about that. You could alternatively tell the TER that 
every newly uploaded extension version has to have a TYPO3 version 
constraint for the maximum of the current rc1 version. Extension 
developers in TER have just to reupload their extensions every 6 months 
if they are working on the current version.

Greetz