Sync perlfaq.

[p5sagit/p5-mst-13.2.git] / pod / perlopentut.pod

diff --git a/pod/perlopentut.pod b/pod/perlopentut.pod
index 0b60096..f023434 100644 (file)
--- a/pod/perlopentut.pod
+++ b/pod/perlopentut.pod
@@ -67,7 +67,7 @@ examples would effectively mean
 which is definitely not what you want.
 
 The other important thing to notice is that, just as in the shell,
-any white space before or after the filename is ignored.  This is good,
+any whitespace before or after the filename is ignored.  This is good,
 because you wouldn't want these to do different things:
 
     open INFO,   "<datafile"   
@@ -82,7 +82,7 @@ in from a different file, and forget to trim it before opening:
 
 This is not a bug, but a feature.  Because C<open> mimics the shell in
 its style of using redirection arrows to specify how to open the file, it
-also does so with respect to extra white space around the filename itself
+also does so with respect to extra whitespace around the filename itself
 as well.  For accessing files with naughty names, see 
 L<"Dispelling the Dweomer">.
 
@@ -332,7 +332,7 @@ C<sysopen> takes 3 (or 4) arguments.
 
 The HANDLE argument is a filehandle just as with C<open>.  The PATH is
 a literal path, one that doesn't pay attention to any greater-thans or
-less-thans or pipes or minuses, nor ignore white space.  If it's there,
+less-thans or pipes or minuses, nor ignore whitespace.  If it's there,
 it's part of the path.  The FLAGS argument contains one or more values
 derived from the Fcntl module that have been or'd together using the
 bitwise "|" operator.  The final argument, the MASK, is optional; if
@@ -364,7 +364,7 @@ added to the sysopen() flags because large files are the default.)
 Here's how to use C<sysopen> to emulate the simple C<open> calls we had
 before.  We'll omit the C<|| die $!> checks for clarity, but make sure
 you always check the return values in real code.  These aren't quite
-the same, since C<open> will trim leading and trailing white space,
+the same, since C<open> will trim leading and trailing whitespace,
 but you'll get the idea.
 
 To open a file for reading:
@@ -521,7 +521,7 @@ working directory, slash the directory separator, and disallows ASCII
 NULs within a valid filename.  Most systems follow these conventions,
 including all POSIX systems as well as proprietary Microsoft systems.
 The only vaguely popular system that doesn't work this way is the
-proprietary Macintosh system, which uses a colon where the rest of us
+"Classic" Macintosh system, which uses a colon where the rest of us
 use a slash.  Maybe C<sysopen> isn't such a bad idea after all.
 
 If you want to use C<< <ARGV> >> processing in a totally boring
@@ -723,7 +723,9 @@ With descriptors that you haven't opened using C<sysopen>, such as
 sockets, you can set them to be non-blocking using C<fcntl>:
 
     use Fcntl;
-    fcntl(Connection, F_SETFL, O_NONBLOCK) 
+    my $old_flags = fcntl($handle, F_GETFL, 0) 
+        or die "can't get flags: $!";
+    fcntl($handle, F_SETFL, $old_flags | O_NONBLOCK) 
         or die "can't set non blocking: $!";
 
 Rather than losing yourself in a morass of twisting, turning C<ioctl>s,