Coding Standards

Use the PEAR coding standard (22/04/2009 - see php-qa list for concerns)
Deviation from the standard: Do not use _ prefix for private members. (Reason: too much re-work to existing code)
We prefix classnames with rt (Reason: avoid name conflicts with built-in PHP classes)
We do not follow the original PEAR class naming scheme (Reason: we use autoload and name prefixes, so we can keep classnames shorter than DIR_DIR_DIR_CLASS)
We will not include both File and Class doc blocks. (Reason: Only ever one class per file)
Don't use private, always use protected instead. (Requested by Greg)