[TYPO3-50-general] File name conventions for classes and interfaces

Robert Lemke robert at typo3.org
Tue Dec 5 19:32:05 CET 2006

Hi again.

You might think I only mull over naming files and classes ... Well, the 
last days I have intensively been thinking about object management (and 
I'm not through with it yet). What I now stumbled over is again the 
naming of a directory: "{packagename}/components".

The purpose of this directory is to store the php code of each package, 
namely the classes and interfaces, one per file. They can of course be 
components, but if you take it seriously, components are not just any 
kind of objects [1]. We can't call the directory "classes" either, 
because it'll contain interfaces as well. Anything like "plugins", 
"modules" etc. doesn't fit either, because virtually any kind of php 
code may be in there.

One solution could be calling just "source", "sourcecode" or "code" [2].
Another variant would be creating two directories, "classes" and 

My favourite currently is "source". What's your's?


[1] http://en.wikipedia.org/wiki/Software_componentry
[2] http://en.wikipedia.org/wiki/Source_code

More information about the TYPO3-project-5_0-general mailing list