cvs: peardoc /en/chapters standards.xml

alexmerz Mon Jan 28 06:01:31 2002 EDT Modified files: /peardoc/en/chapters standards.xml Log: typo, patch by Hayk Chamyan Index: peardoc/en/chapters/standards.xml diff -u peardoc/en/chapters/standards.xml:1.3 peardoc/en/chapters/standards.xml:1.4 --- peardoc/en/chapters/standards.xml:1.3 Thu Jan 24 09:05:32 2002 +++ peardoc/en/chapters/standards.xml Mon Jan 28 06:01:29 2002 @@ -1,5 +1,5 @@ <?xml encoding="iso-8859-1"?> -<!-- $Revision: 1.3 $ --> +<!-- $Revision: 1.4 $ --> <chapter id="standards"> <title>Coding Standards</title> <note> @@ -29,10 +29,10 @@ </para> <para>Here are vim rules for the same thing: <programlisting role="vim"> - set expandtab - set shiftwidth=4 + set expandtab + set shiftwidth=4 set softtabstop=4 - set tabstop=4 + set tabstop=4 </programlisting> </para> </sect1> @@ -133,11 +133,11 @@ } else { $dsninfo = DB::parseDSN($dsn); } - + if (!$dsninfo || !$dsninfo['phptype']) { return $this->raiseError(); } - + return true; } </programlisting> @@ -182,7 +182,7 @@ around the filename to be included. </simpara> </note> - </para> + </para> </sect1> <sect1 id="standards.tags"> @@ -222,8 +222,8 @@ // &dollar;Id&dollar; </programlisting> </para> - <para> - There's no hard rule to determine when a new code contributer + <para> + There's no hard rule to determine when a new code contributor should be added to the list of authors for a given source file. In general, their changes should fall into the "substantial" category (meaning somewhere around 10% to 20% of code changes). @@ -254,7 +254,7 @@ <note> <simpara> We have a custom $Horde tag in Horde cvs to track our versions - seperately; we could do the same and make a $PEAR tag, that + separately; we could do the same and make a $PEAR tag, that would remain even if PEAR files were put into another source control system, etc...] </simpara> @@ -398,7 +398,7 @@ Private class members (meaning class members that are intented to be used only from within the same class in which they are declared; PHP does not yet support truly-enforceable private - namespaces) are preceeded by a single underscore. For example: + namespaces) are preceded by a single underscore. For example: <informaltable> <tgroup cols="3"> <tbody> @@ -416,7 +416,7 @@ <title>Constants</title> <para> Constants should always be all-uppercase, with underscores to - seperate words. Prefix constant names with the uppercased name + separate words. Prefix constant names with the uppercased name of the class/package they are used in. For example, the constants used by the <literal>DB::</literal> package all begin with "<literal>DB_</literal>".