cvs: peardoc /en language-snippets.ent /en/chapters parts.xml /en/contributing howto.xml /en/packages/templates itx.xml

From: Date: Thu, 24 Jan 2002 20:52:32 +0000
Subject: cvs: peardoc /en language-snippets.ent /en/chapters parts.xml /en/contributing howto.xml /en/packages/templates itx.xml
Groups: php.pear.cvs 
Request: Send a blank email to pear-cvs+get-2095@lists.php.net to get a copy of this message
jan Thu Jan 24 15:52:32 2002 EDT Modified files: /peardoc/en language-snippets.ent /peardoc/en/chapters parts.xml /peardoc/en/contributing howto.xml /peardoc/en/packages/templates itx.xml Log: - adding &link.coding-standards; and using it. Index: peardoc/en/language-snippets.ent diff -u peardoc/en/language-snippets.ent:1.2 peardoc/en/language-snippets.ent:1.3 --- peardoc/en/language-snippets.ent:1.2 Mon Dec 17 13:30:28 2001 +++ peardoc/en/language-snippets.ent Thu Jan 24 15:52:30 2002 @@ -1,4 +1,4 @@ -<!-- $Revision: 1.2 $ --> +<!-- $Revision: 1.3 $ --> <!ENTITY warn.experimental '<warning><simpara>This module is <emphasis>EXPERIMENTAL</emphasis>. That means, that the behaviour of these functions, these function names, in concreto ANYTHING documented here can change in a future release of this package WITHOUT NOTICE. Be warned, and use this module at your own risk.</simpara></warning>'> <!ENTITY warn.experimental.func '<warning><simpara>This function is <emphasis>EXPERIMENTAL</emphasis>. That means, that the behaviour of this function, this function name, in concreto ANYTHING documented here can change in a future release of this package WITHOUT NOTICE. Be warned, and use this function at your own risk.</simpara></warning>'> @@ -8,3 +8,4 @@ <!ENTITY return.success 'Returns &true; on succes, &false; on failure.'> <!ENTITY return.falseproblem '<warning><simpara>This function may return &false;, but may also return a value evaluating to &false; in a simple if statement. Please use <link linkend="language.operators.comparison">the === operator</link> for testing the return value of this function.</simpara></warning>'> +<!ENTITY link.coding-standards 'PEAR <link linkend="standards">coding standards.</link>'> Index: peardoc/en/chapters/parts.xml diff -u peardoc/en/chapters/parts.xml:1.1 peardoc/en/chapters/parts.xml:1.2 --- peardoc/en/chapters/parts.xml:1.1 Sat Dec 29 05:58:25 2001 +++ peardoc/en/chapters/parts.xml Thu Jan 24 15:52:31 2002 @@ -1,5 +1,5 @@ <?xml encoding="iso-8859-1"?> -<!-- $Revision: 1.1 $ --> +<!-- $Revision: 1.2 $ --> <chapter id="parts"> <title>PEAR's three parts</title> <simpara> @@ -21,12 +21,12 @@ <simpara> The extended part of PEAR contains the general packages written in PHP or extensions to PHP written in C that are compliant to - the PEAR <link linkend="standards">coding standards</link>. + the &link.coding-standards;. </simpara> <para> The packages from the extended part are published via the PEAR - installation tools and have to correspond to the - <link linkend="standards">coding standards.</link> + installation tools and have to correspond to the &link.coding-standards; + </para> </sect1> @@ -34,8 +34,7 @@ <title>PECL</title> <simpara> PECL is the repository for PHP extensions written in C, that are - not compliant to the PEAR <link linkend="standards">coding - standards.</link> + not compliant to the &link.coding-standards;. </simpara> <para> PECL has been set up to be a repository for the extension tree Index: peardoc/en/contributing/howto.xml diff -u peardoc/en/contributing/howto.xml:1.1 peardoc/en/contributing/howto.xml:1.2 --- peardoc/en/contributing/howto.xml:1.1 Fri Dec 14 12:10:58 2001 +++ peardoc/en/contributing/howto.xml Thu Jan 24 15:52:31 2002 @@ -1,5 +1,5 @@ <?xml encoding="iso-8859-1"?> -<!-- $Revision: 1.1 $ --> +<!-- $Revision: 1.2 $ --> <chapter id="contributing-howto"> <title>How to contribute to PEAR</title> <simpara> @@ -28,9 +28,8 @@ <para> <itemizedlist> <listitem> - <simpara>Your code has to be compliant to the <ulink url=" - standards.php">PEAR coding standards</ulink>. This is - necessary because PEAR has the aim to provide well suited + <simpara>Your code has to be compliant to the &link.coding-standards;. + This is necessary because PEAR has the aim to provide well suited and standards compliant source code.</simpara> </listitem> Index: peardoc/en/packages/templates/itx.xml diff -u peardoc/en/packages/templates/itx.xml:1.2 peardoc/en/packages/templates/itx.xml:1.3 --- peardoc/en/packages/templates/itx.xml:1.2 Sat Jan 5 06:25:47 2002 +++ peardoc/en/packages/templates/itx.xml Thu Jan 24 15:52:31 2002 @@ -26,7 +26,7 @@ it is not recommended to start a project based ITX. If you want a PHPLIB-styled template system, then you should use <classname>Template_PHPLIB</classname>, which is the PHPLIB template - system following the PEAR coding standards. + system following the &link.coding-standards;. </para> </refsect1>

« previous php.pear.cvs (#2095) next »