pear:rfc:pear2_standards
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
pear:rfc:pear2_standards [2009/09/20 19:13] – populate Class Naming convention rule based on ratification of Class Naming RFC ashnazg | pear:rfc:pear2_standards [2017/09/22 13:28] (current) – external edit 127.0.0.1 | ||
---|---|---|---|
Line 6: | Line 6: | ||
* Title: PEAR2 Coding Standards | * Title: PEAR2 Coding Standards | ||
- | * Version: | + | * Version: |
* Status: | * Status: | ||
* Type: Standards | * Type: Standards | ||
- | * Last updated: September | + | * Last updated: September |
==== Author(s) Information ==== | ==== Author(s) Information ==== | ||
Line 166: | Line 166: | ||
<? | <? | ||
- | if (!class_exists(" | + | if (!class_exists(" |
throw new \PEAR2\PackageName\Exception(' | throw new \PEAR2\PackageName\Exception(' | ||
', | ', | ||
Line 236: | Line 236: | ||
The only exception to this rule is the Base Package Exception Interface, which is specifically required to be named " | The only exception to this rule is the Base Package Exception Interface, which is specifically required to be named " | ||
- | ==== Package Naming convention ==== | + | |
- | A package naming rule may potentially be added to these standards, if the [[pear/ | + | |
==== Base Exception interface ==== | ==== Base Exception interface ==== | ||
Line 289: | Line 288: | ||
| | ||
try { | try { | ||
- | $p = new PEAR2\PackageName\Foo(); | + | $p = new \PEAR2\PackageName\Foo(); |
| | ||
- | } catch (PEAR2\PackageName\Exception $e) { | + | } catch (\PEAR2\PackageName\Exception $e) { |
echo " | echo " | ||
} | } | ||
Line 312: | Line 311: | ||
... | ... | ||
// retrieve data from info.txt | // retrieve data from info.txt | ||
- | $info = file_get_contents(dirname(__FILE__) . ' | + | $info = file_get_contents(dirname(__FILE__) . '/../ |
?> | ?> | ||
pear/rfc/pear2_standards.txt · Last modified: 2017/09/22 13:28 by 127.0.0.1