cvs: peardoc /en/chapters standards.xml

mj Sun Dec 17 10:15:59 2006 UTC Modified files: /peardoc/en/chapters standards.xml Log: * Added section for the new rule that code must be E_STRICT compatible. http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/standards.xml?r1=1.45&r2=1.46&diff_format=u Index: peardoc/en/chapters/standards.xml diff -u peardoc/en/chapters/standards.xml:1.45 peardoc/en/chapters/standards.xml:1.46 --- peardoc/en/chapters/standards.xml:1.45 Tue Dec 12 19:18:28 2006 +++ peardoc/en/chapters/standards.xml Sun Dec 17 10:15:59 2006 @@ -1,5 +1,5 @@ <?xml version="1.0" encoding="iso-8859-1" ?> -<!-- $Revision: 1.45 $ --> +<!-- $Revision: 1.46 $ --> <chapter id="standards"> <title>Coding Standards</title> @@ -826,6 +826,29 @@ </para> </sect1> + <sect1 id="standards.e_strict"> + <title><literal>E_STRICT</literal>-compatible code</title> + <para> + Starting on 01 January 2007, all new code that is suggested for + inclusion into PEAR must be + <literal>E_STRICT</literal>-compatible. This means that it must + not produce any warnings or errors when PHP's error reporting level + is set to <literal>E_STRICT</literal>. + </para> + <para> + The development of existing packages that are not + <literal>E_STRICT</literal>-compatible can continue as usual. If + however a new <emphasis>major</emphasis> version of the package is + released, this major version must then be + <literal>E_STRICT</literal>-compatible. + </para> + <para> + More details on this part of the Coding Standards can be found in + the corresponding <ulink url="&url.pear.pepr.proposal;419">PEPr + proposal</ulink>. + </para> + </sect1> + <sect1 id="standards.bestpractices"> <title>Best practices</title> <para>