Change 18634 by ams@lustre on 2003/02/02 18:07:01
Subject: [PATCH] pod/perlfunc.pod
From: [EMAIL PROTECTED]
Date: Sun, 2 Feb 2003 16:59:48 +0100
Message-Id: <[EMAIL PROTECTED]>
Affected files ...
... //depot/perl/pod/perlfunc.pod#364 edit
Differences ...
==== //depot/perl/pod/perlfunc.pod#364 (text) ====
Index: perl/pod/perlfunc.pod
--- perl/pod/perlfunc.pod#363~18482~ Tue Jan 14 13:41:04 2003
+++ perl/pod/perlfunc.pod Sun Feb 2 10:07:01 2003
@@ -4812,13 +4812,13 @@
patterns that vary at runtime. (To do runtime compilation only once,
use C</$variable/o>.)
-As a special case, specifying a PATTERN of space (C<' '>) will split on
-white space just as C<split> with no arguments does. Thus, C<split(' ')> can
-be used to emulate B<awk>'s default behavior, whereas C<split(/ /)>
+As a special case, specifying a PATTERN of space (S<C<' '>>) will split on
+white space just as C<split> with no arguments does. Thus, S<C<split(' ')>> can
+be used to emulate B<awk>'s default behavior, whereas S<C<split(/ /)>>
will give you as many null initial fields as there are leading spaces.
-A C<split> on C</\s+/> is like a C<split(' ')> except that any leading
+A C<split> on C</\s+/> is like a S<C<split(' ')>> except that any leading
whitespace produces a null first field. A C<split> with no arguments
-really does a C<split(' ', $_)> internally.
+really does a S<C<split(' ', $_)>> internally.
A PATTERN of C</^/> is treated as if it were C</^/m>, since it isn't
much use otherwise.
End of Patch.
