torben          Wed Feb 13 17:00:01 2002 EDT

  Modified files:              
    /phpdoc/en/functions        network.xml 
  Log:
  Note that the 3rd and 4th args to fsockopen() are always passed by ref.
  Closes Bug #8087.
  
  
Index: phpdoc/en/functions/network.xml
diff -u phpdoc/en/functions/network.xml:1.55 phpdoc/en/functions/network.xml:1.56
--- phpdoc/en/functions/network.xml:1.55        Wed Feb 13 16:53:10 2002
+++ phpdoc/en/functions/network.xml     Wed Feb 13 16:59:59 2002
@@ -1,5 +1,5 @@
 <?xml version="1.0" encoding="iso-8859-1"?>
-<!-- $Revision: 1.55 $ -->
+<!-- $Revision: 1.56 $ -->
  <reference id="ref.network">
   <title>Network Functions</title>
   <titleabbrev>Network</titleabbrev>
@@ -171,14 +171,15 @@
      If the call fails, it will return &false; and if the optional
      <parameter>errno</parameter> and <parameter>errstr</parameter>
      arguments are present they will be set to indicate the actual
-     system level error that occurred on the system-level
-     <literal>connect()</literal> call. If the returned errno is
-     <literal>0</literal> and the function returned &false;, it is an
-     indication that the error occurred before the
-     <literal>connect()</literal> call. This is most likely due to a
-     problem initializing the socket. Note that the
-     <parameter>errno</parameter> and <parameter>errstr</parameter>
-     arguments must be passed by reference.
+     system level error that occurred in the system-level
+     <literal>connect()</literal> call. If the value returned in
+     <parameter>errno</parameter> is <literal>0</literal> and the
+     function returned &false;, it is an indication that the error
+     occurred before the <literal>connect()</literal> call. This is
+     most likely due to a problem initializing the socket. Note that
+     the <parameter>errno</parameter> and
+     <parameter>errstr</parameter> arguments will always be passed by
+     reference.
     </para>
     <para>
      Depending on the environment, the Unix domain or the optional


Reply via email to