Useful Links Official Site http:/­/ww­w.p­hp-­fig.org Accepted Standards PSR-0 Autolo­ading Standard http:/­/ww­w.p­hp-­fig.or­g/p­sr/­psr-0/ PSR-1 Basic Coding Standard http:/­/ww­w.p­hp-­fig.or­g/p­sr/­psr-1/ PSR-2 Coding Style Guide http:/­/ww­w.p­hp-­fig.or­g/p­sr/­psr-2/ PSR-3 Logger Interface http:/­/ww­w.p­hp-­fig.or­g/p­sr/­psr-3/ PSR-4 Improved Autolo­ading http:/­/ww­w.p­hp-­fig.or­g/p­sr/­psr-4/ PSR-0 - Overview A fully-­qua­lified namespace and class must have the following structure \<V­endor Name>­\(<N­ame­spa­ce>­\)*­<Class Name> Each namespace must have a top-level namespace ("Vendor Name"). Each namespace can have as many sub-na­mes­paces as it wishes. Each namespace separator is converted to a DIRECT­ORY­_SE­PARATOR when loading from the file system. Each _ character in the CLASS NAME is converted to a DIRECT­ORY­_SE­PAR­ATOR. The _ character has no special meaning in the namespace. The fully-­qua­lified namespace and class is suffixed with .php when loading from the file system. Alphabetic characters in vendor names, namesp­aces, and class names may be of any combin­ation of lower case and upper case. PSR-1 - Overview Files MUST use only <?php and <?= tags. Files MUST use only UTF-8 without BOM for PHP code. Files SHOULD either declare symbols (classes, functions, constants, etc.) or cause side-e­ffects (e.g. generate output, change .ini settings, etc.) but SHOULD NOT do both. Namespaces and classes MUST follow PSR-0. Class names MUST be declared in Studly­Caps. Class constants MUST be declared in all upper case with underscore separa­tors. Method names MUST be declared in camelCase. PSR-2 - Overview Code MUST follow PSR-1. Code MUST use 4 spaces for indenting, not tabs. There MUST NOT be a hard limit on line length; the soft limit MUST be 120 charac­ters; lines SHOULD be 80 characters or less. There MUST be one blank line after the namespace declar­ation, and there MUST be one blank line after the block of use declar­ations. Opening braces for classes MUST go on the next line, and closing braces MUST go on the next line after the body. Opening braces for methods MUST go on the next line, and closing braces MUST go on the next line after the body. Visibility MUST be declared on all properties and methods; abstract and final MUST be declared before the visibi­lity; static MUST be declared after the visibi­lity. Control structure keywords MUST have one space after them; method and function calls MUST NOT. Opening braces for control structures MUST go on the same line, and closing braces MUST go on the next line after the body. Opening parent­heses for control structures MUST NOT have a space after them, and closing parent­heses for control structures MUST NOT have a space before. PSR-2 - General Code MUST follow all rules outlined in PSR-1. All PHP files MUST use the Unix LF (linefeed) line ending. All PHP files MUST end with a single blank line. The closing ?> tag MUST be omitted from files containing only PHP. There MUST NOT be a hard limit on line length. The soft limit on line length MUST be 120 charac­ters; automated style checkers MUST warn but MUST NOT error at the soft limit. Lines SHOULD NOT be longer than 80 charac­ters; lines longer than that SHOULD be split into multiple subsequent lines of no more than 80 characters each. There MUST NOT be trailing whitespace at the end of non-blank lines. Blank lines MAY be added to improve readab­ility and to indicate related blocks of code. There MUST NOT be more than one statement per line. Code MUST use an indent of 4 spaces, and MUST NOT use tabs for indenting. PHP keywords MUST be in lower case. The PHP constants true, false, and null MUST be in lower case. PSR-2 - Namespace and Use Declar­ations When present, there MUST be one blank line after the namespace declar­ation. When present, all use declar­ations MUST go after the namespace declar­ation. There MUST be one use keyword per declar­ation. There MUST be one blank line after the use block.

PSR-2 - Classes, Proper­ties, and Methods The extends and implements keywords MUST be declared on the same line as the class name. The opening brace for the class MUST go on its own line; the closing brace for the class MUST go on the next line after the body. Lists of implements MAY be split across multiple lines, where each subsequent line is indented once. When doing so, the first item in the list MUST be on the next line, and there MUST be only one interface per line. Visibility MUST be declared on all proper­ties. The var keyword MUST NOT be used to declare a property. There MUST NOT be more than one property declared per statement. Property names SHOULD NOT be prefixed with a single underscore to indicate protected or private visibi­lity. Visibility MUST be declared on all methods. Method names SHOULD NOT be prefixed with a single underscore to indicate protected or private visibi­lity. Method names MUST NOT be declared with a space after the method name. The opening brace of a method MUST go on its own line, and the closing brace MUST go on the next line following the body. There MUST NOT be a space after the opening parent­hesis of a method, and there MUST NOT be a space before the closing parent­hesis. In the argument list, there MUST NOT be a space before each comma, and there MUST be one space after each comma. Method arguments with default values MUST go at the end of the argument list. Argument lists MAY be split across multiple lines, where each subsequent line is indented once. When doing so, the first item in the list MUST be on the next line, and there MUST be only one argument per line. When the argument list is split across multiple lines, the closing parent­hesis and opening brace MUST be placed together on their own line with one space between them. When present, the abstract and final declar­ations MUST precede the visibility declar­ation. When present, the static declar­ation MUST come after the visibility declar­ation. When making a method or function call, there MUST NOT be a space between the method or function name and the opening parent­hesis, there MUST NOT be a space after the opening parent­hesis, and there MUST NOT be a space before the closing parent­hesis. In the argument list, there MUST NOT be a space before each comma, and there MUST be one space after each comma. PSR-2 - Control Structures There MUST be one space after the control structure keyword There MUST NOT be a space after the opening parent­hesis There MUST NOT be a space before the closing parent­hesis There MUST be one space between the closing parent­hesis and the opening brace The structure body MUST be indented once The closing brace MUST be on the next line after the body The body of each structure MUST be enclosed by braces. The keyword elseif SHOULD be used instead of else if. The case statement MUST be indented once from switch, and the break keyword (or other termin­ating keyword) MUST be indented at the same level as the case body. There MUST be a comment such as // no break when fall-t­hrough is intent­ional in a non-empty case body. PSR-2 - Closures Closures MUST be declared with a space after the function keyword, and a space before and after the use keyword. The opening brace MUST go on the same line, and the closing brace MUST go on the next line following the body. There MUST NOT be a space after the opening parent­hesis of the argument list or variable list, and there MUST NOT be a space before the closing parent­hesis of the argument list or variable list. In the argument list and variable list, there MUST NOT be a space before each comma, and there MUST be one space after each comma. Closure arguments with default values MUST go at the end of the argument list. Argument lists and variable lists MAY be split across multiple lines, where each subsequent line is indented once. When doing so, the first item in the list MUST be on the next line, and there MUST be only one argument or variable per line. When the ending list (whether or arguments or variables) is split across multiple lines, the closing parent­hesis and opening brace MUST be placed together on their own line with one space between them.