summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorTom Phoenix <rootbeer@teleport.com>1998-06-18 16:37:32 -0700
committerGurusamy Sarathy <gsar@cpan.org>1998-06-21 00:05:01 +0000
commitfbb426e4e4fa9111602f64c566d240fa509dea6f (patch)
tree58426a7367db0aad690393c33ac23275ca83c67c /pod
parentd720c4410d3a0730e373566db978e2b5789690e0 (diff)
downloadperl-fbb426e4e4fa9111602f64c566d240fa509dea6f.tar.gz
docs creating files via open
Message-ID: <Pine.GSO.3.96.980618231856.17544S-100000@user2.teleport.com> p4raw-id: //depot/perl@1168
Diffstat (limited to 'pod')
-rw-r--r--pod/perlfunc.pod5
1 files changed, 3 insertions, 2 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 25a97ffddb..31367ed07b 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -2127,8 +2127,9 @@ to open.)
If the filename begins with '<' or nothing, the file is opened for input.
If the filename begins with '>', the file is truncated and opened for
-output. If the filename begins with '>>', the file is opened for
-appending. You can put a '+' in front of the '>' or '<' to indicate that
+output, being created if necessary. If the filename begins with '>>',
+the file is opened for appending, again being created if necessary.
+You can put a '+' in front of the '>' or '<' to indicate that
you want both read and write access to the file; thus '+<' is almost
always preferred for read/write updates--the '+>' mode would clobber the
file first. You can't usually use either read-write mode for updating