[TYPO3-core] Feature #9633: Implement autoloading for TYPO3

[Oliver Hader]

Hi Dmitry,

Dmitry Dulepov schrieb:
> Hi!
> 
> Oliver Hader wrote:
>> The patch of this RFC is base on your and Dmitry's first patches...
> 
> I still like my version more because it is automatic, simple and does not require complex logic. The simpler, the better.

The patch of the current RFC is partly based on your work. However,
using a serialized array (different in FE and BE disposal) that contains
all classes of core and extension files leads to some problems:
* another deserialization of a large string on every request takes some time
* using the autoloader during development (implementing and
reviewing/testing) takes some more time, since the whole registry file
has to be rebuild manually to enable autoloading for the new stuff
* rebuilding the registry on installing new extensions or removing some
takes some time when many extensions are installed - it may cause
"memory exceeded" and "max. script runtime exceeded" errors

(please see the message I've written in reply to Bernhard on 2009-05-01
at 18:00 to get an overview how it works in the patch of this RFC)

> My patch should work with any extension that follows v4 CGL. If Extbase does not follow our CGL, Extbase has to be updated to follow CGL.

Yes, indeed! But the reason for that is, that it does not use any v4
naming scheme during autoloading of classes, they are just taken from
the mapping registry file...

To all others:
Currently there is an internal discussion about a new "Tx_" prefix
concerning changes to the still unpublished new CGL.
Extbase defines the bridge between extension development in TYPO3 4.x
and TYPO3 5.0. Following this new way, allows one to reuse (after some
smaller corrections) v4 extensions when TYPO3 5.0 is released. Thus,
it's possible to create forward compatible extensions with TYPO3 4.3!
That's just FYI for parties that did not know about the background of
Extbase.

olly
-- 
Oliver Hader
TYPO3 Release Manager 4.3