philip          Sat Jan 19 20:09:31 2002 EDT

  Modified files:              
    /phpdoc/en/language control-structures.xml 
  Log:
  include: minor textual changes.
  
  
Index: phpdoc/en/language/control-structures.xml
diff -u phpdoc/en/language/control-structures.xml:1.52 
phpdoc/en/language/control-structures.xml:1.53
--- phpdoc/en/language/control-structures.xml:1.52      Sat Jan 19 07:01:10 2002
+++ phpdoc/en/language/control-structures.xml   Sat Jan 19 20:09:30 2002
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.52 $ -->
+<!-- $Revision: 1.53 $ -->
  <chapter id="control-structures">
   <title>Control Structures</title>
 
@@ -1098,7 +1098,7 @@
      failure.  <function>include</function> produces a 
      <link linkend="internal.e-warning">Warning</link> while 
<function>require</function>
      results in a <link linkend="internal.e-error">Fatal Error</link>.
-     In other words, don't hesitate to use <function>require</function> if you want 
+     In other words, use <function>require</function> if you want 
      a missing file to halt processing of the page.  <function>include</function> 
does 
      not behave this way, the script will continue regardless.  Be sure to have an 
      appropriate <link linkend="ini.include-path">include_path</link> setting as well.
@@ -1292,7 +1292,7 @@
 
 ?>
 
-getfoo.php
+testreturns.php
 <?php
 
 $foo = include 'return.php';
@@ -1309,8 +1309,8 @@
     </example>
    </para>
    <simpara>
-    <literal>$bar</literal> is the value (1) because the include was successful.  
-    Notice the difference between the above examples.  The first uses 
+    <literal>$bar</literal> is the value <literal>1</literal> because the include 
+    was successful.  Notice the difference between the above examples.  The first 
+uses 
     <function>return</function> within the included file while the other does not.  
     A few other ways to "include" files into variables are with 
     <function>fopen</function>, <function>file</function> or by using 


Reply via email to