[TYPO3-project-4-3] Splitting t3lib_div and having autoloader instead of inclusions

[Martin Kutschker]

Ingo Renner schrieb:
> Steffen Kamper wrote:
> 
>> may be we can learn something from Drupal
>>
>> http://api.drupal.org/api/group/registry/7
> 
> I just had a look at it, and hey, this is cool stuff and provides quite
> a few new ideas for our autoloader!

But it relies on the database for implementation. Do we really need such
a heavyweight code? DB down => auto loader breaks? Doesn't sound too
compelling to me.

I thought that we only would need a kind of registry to define a context
 (eg t3lib, typo3/classes or tslib). Within each context a naming scheme
would do the basic loading but each context could provide helper code
where for some reason the naming scheme doesn't work.

Maybe Drupal spreads its classes and function all over the file system,
but TYPO3 has it already clustered in a few directories, so I don't see
the need for PHP file parsing (see _registry_rebuild).

Masi