cvs: peardoc /en/chapters pear2cs.xml

arnaud		Mon Nov 26 22:29:17 2007 UTC

  Modified files:              
    /peardoc/en/chapters	pear2cs.xml 
  Log:
  improve docbook code
  
  
http://cvs.php.net/viewvc.cgi/peardoc/en/chapters/pear2cs.xml?r1=1.2&r2=1.3&diff_format=u
Index: peardoc/en/chapters/pear2cs.xml
diff -u peardoc/en/chapters/pear2cs.xml:1.2 peardoc/en/chapters/pear2cs.xml:1.3
--- peardoc/en/chapters/pear2cs.xml:1.2	Mon Nov 26 22:19:07 2007
+++ peardoc/en/chapters/pear2cs.xml	Mon Nov 26 22:29:17 2007
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="utf-8" ?>
-<!-- $Revision: 1.2 $ -->
+<!-- $Revision: 1.3 $ -->
  <chapter id="pear2cs">
   <chapterinfo>
    <date>2007-11-26</date>
@@ -69,14 +69,14 @@
    </para>
 
    <para>
-    require_once introduces a rigidity to package structure that limits the
+    <functionname>require_once</functionname> introduces a rigidity to package structure that limits the
     possible uses of a PEAR package.
     Some of the problems:
 
     <itemizedlist>
      <listitem>
       <simpara>
-     require_once can introduce up to a 10% performance penalty on
+     <functionname>require_once</functionname> can introduce up to a 10% performance penalty on
      high-volume sites using multi-processor web servers due to increased
      latency.  However, most users would experience at most 2% performance
      penalty on single-processor systems (as measured by Yahoo! engineer
@@ -94,14 +94,14 @@
      </listitem>
      <listitem>
       <simpara>
-     when top-level require_once is mixed with conditional require_once, this
+     when top-level <functionname>require_once</functionname> is mixed with conditional <functionname>require_once</functionname>, this
      can result in code that is uncacheable by opcode caches such as APC,
      which will be bundled with PHP 6.
       </simpara>
      </listitem>
      <listitem>
       <simpara>
-     relative require_once requires that include_path already be set up to
+     relative <functionname>require_once</functionname> requires that include_path already be set up to
      the correct value, making it impossible to use a package without proper
      include_path
       </simpara>
@@ -110,7 +110,7 @@
    </para>
 
    <para>
-    Some of the benefits of require_once:
+    Some of the benefits of <functionname>require_once</functionname>:
     <itemizedlist>
      <listitem>
       <simpara>
@@ -128,7 +128,7 @@
    </para>
 
    <para>
-    The removal of require_once necessitates another method for loading
+    The removal of <functionname>require_once</functionname> necessitates another method for loading
     internal dependencies, both files within a package and external files.
     This proposal introduces 2 possible methods for doing this:
     <itemizedlist>
@@ -158,10 +158,10 @@
     PEAR2_Exception and PEAR2_Autoload).
     <programlisting role="php">
      <![CDATA[
-       <?php
-         require '/full/path/to/PEAR2/Autoload.php';
-         // now you can start using all PEAR2 packages
-       ?>
+<?php
+  require '/full/path/to/PEAR2/Autoload.php';
+  // now you can start using all PEAR2 packages
+?>
      ]]>
     </programlisting>
     PEAR2/Autoload.php automatically sets up include_path if it does not
@@ -184,10 +184,10 @@
     </para>
      <programlisting role="php">
      <![CDATA[
-       <?php
-       namespace PEAR2;
-       class MyClass {}
-       ?>
+<?php
+namespace PEAR2;
+class MyClass {}
+?>
      ]]>
      </programlisting>
     <para>
@@ -197,10 +197,10 @@
     </para>
      <programlisting role="php">
      <![CDATA[
-       <?php
-       namespace PEAR2::HTTP;
-       class Request {}
-       ?>
+<?php
+namespace PEAR2::HTTP;
+class Request {}
+?>
      ]]>
      </programlisting>
     <para>