[TYPO3-core] RFC #12067: Remove ext_autoload.php files for extensions using Extbase naming convention
Xavier Perseguers
typo3 at perseguers.ch
Fri Sep 25 22:09:45 CEST 2009
Hi,
This is a SVN patch request
Type: Feature/Enhancement
Branches: trunk only
Bugtracker reference:
http://bugs.typo3.org/view.php?id=12067
Problem:
The use of ext_autoload.php files was once supposed to be used only for old-fashioned extensions that did not used Extbase naming convention (Classes directory, class component parts as subdirectories).
Nowadays, all new extensions (starting with Extbase itself) are polluted with a never-ending growing ext_autoload.php file and we slowly start adding all our classes there to be sure all will work
fine without exactly knowing what really needs to be in.
The patch allows not less than the removal of the ext_autoload.php file for all extensions sticking to using only the Extbase naming convention. This file may still be used for some third-party
classes that may be included in a pure Extbase-styled extension.
Note 1: This has nothing to do with extensions relying on Extbase itself, only on its naming convention.
Note 2: Fine-tuning of style and the rest may apply
How-to test:
e.g., delete file EXT:extbase/ext_autoload.php and see that it still works
--
Xavier Perseguers
http://xavier.perseguers.ch/en
One contribution a day keeps the fork away
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: 12067.diff
Url: http://lists.netfielders.de/pipermail/typo3-team-core/attachments/20090925/fbf36f62/attachment.txt
More information about the TYPO3-team-core
mailing list