Doctrine_manual-1-2-en

Chapter 32: Coding

Chapter 32: Coding Standards 382 Naming Conventions Classes The Doctrine ORM Framework uses the same class naming convention as PEAR and Zend framework, where the names of the classes directly map to the directories in which they are stored. The root level directory of the Doctrine Framework is the "Doctrine/" directory, under which all classes are stored hierarchially. Class names may only contain alphanumeric characters. Numbers are permitted in class names but are discouraged. Underscores are only permitted in place of the path separator, eg. the filename "Doctrine/Table/Exception.php" must map to the class name "Doctrine_Table_Exception". If a class name is comprised of more than one word, the first letter of each new word must be capitalized. Successive capitalized letters are not allowed, e.g. a class "XML_Reader" is not allowed while "Xml_Reader" is acceptable. Interfaces Interface classes must follow the same conventions as other classes (see above). They must also end with the word "Interface" (unless the interface is approved not to contain it such as Doctrine_Overloadable). Some examples: Examples • Doctrine_Adapter_Interface • Doctrine_EventListener_Interface Filenames For all other files, only alphanumeric characters, underscores, and the dash character ("-") are permitted. Spaces are prohibited. Any file that contains any PHP code must end with the extension ".php". These examples show the acceptable filenames for containing the class names from the examples in the section above: • Doctrine/Adapter/Interface.php • Doctrine/EventListener/Interface File names must follow the mapping to class names described above. Functions and Methods Function names may only contain alphanumeric characters and underscores are not permitted. Numbers are permitted in function names but are highly discouraged. They must always start with a lowercase letter and when a function name consists of more than one word, the first letter of each new word must be capitalized. This is commonly called the "studlyCaps" or "camelCaps" method. Verbosity is encouraged and function names should be as verbose as is practical to enhance the understandability of code. For object-oriented programming, accessors for objects should always be prefixed with either "get" or "set". This applies to all classes except for Doctrine_Record which has some accessor methods prefixed with 'obtain' and 'assign'. The reason for this is that since all user defined ActiveRecords inherit Doctrine_Record, it should populate the get / set namespace as little as possible. ----------------- Brought to you by

Chapter 32: Coding Standards 383 Functions in the global scope ("floating functions") are NOT permmitted. All static functions should be wrapped in a static class. Variables Variable names may only contain alphanumeric characters. Underscores are not permitted. Numbers are permitted in variable names but are discouraged. They must always start with a lowercase letter and follow the "camelCaps" capitalization convention. Verbosity is encouraged. Variables should always be as verbose as practical. Terse variable names such as "$i" and "$n" are discouraged for anything other than the smallest loop contexts. If a loop contains more than 20 lines of code, the variables for the indices need to have more descriptive names. Within the framework certain generic object variables should always use the following names: Object type Doctrine_Connection $conn Doctrine_Collection $coll Doctrine_Manager Doctrine_Query $q Variable name $manager There are cases when more descriptive names are more appropriate (for example when multiple objects of the same class are used in same context), in that case it is allowed to use different names than the ones mentioned. Constants Constants may contain both alphanumeric characters and the underscore. They must always have all letters capitalized. For readablity reasons, words in constant names must be separated by underscore characters. For example, ATTR_EXC_LOGGING is permitted but ATTR_EXCLOGGING is not.Constants must be defined as class members by using the "const" construct. Defining constants in the global scope with "define" is NOT permitted. class Doctrine_SomeClass { const MY_CONSTANT = 'something'; } Listing 32-1 echo $Doctrine_SomeClass::MY_CONSTANT; Record Columns All record columns must be in lowercase and usage of underscores(_) are encouraged for columns that consist of more than one word. class User { public function setTableDefinition() { $this->hasColumn('home_address', 'string'); } } Listing 32-2 ----------------- Brought to you by