summaryrefslogtreecommitdiff
path: root/pod/perlopentut.pod
diff options
context:
space:
mode:
authorOffer Kaye <offer.kaye@gmail.com>2005-03-17 09:47:36 -0500
committerH.Merijn Brand <h.m.brand@xs4all.nl>2005-03-29 07:01:11 +0000
commit6b0ac556af9eedace4d32a9b51232914d1118023 (patch)
treea2811d49ea035c77bacb6f7a3e5d7e8edf16b01d /pod/perlopentut.pod
parenta212c8b5d0b264f0c7351db7e22b3b1b1178ca8b (diff)
downloadperl-6b0ac556af9eedace4d32a9b51232914d1118023.tar.gz
Make the spelling of whitespace (vs white-space and white space)
more consistent Message-ID: <5694250503171147668e73c7@mail.gmail.com> p4raw-id: //depot/perl@24090
Diffstat (limited to 'pod/perlopentut.pod')
-rw-r--r--pod/perlopentut.pod8
1 files changed, 4 insertions, 4 deletions
diff --git a/pod/perlopentut.pod b/pod/perlopentut.pod
index 72d91b73a3..f023434ed3 100644
--- 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: