In perl.git, the branch blead has been updated
<http://perl5.git.perl.org/perl.git/commitdiff/f26064794a6949d593fcd01d326c28a09f3088f0?hp=178122f6e0bac976a9e16e3553b9469414d70f3c>
- Log -----------------------------------------------------------------
commit f26064794a6949d593fcd01d326c28a09f3088f0
Author: Lukas Mai <l....@web.de>
Date: Sun Sep 18 09:50:16 2016 +0200
perlsub: scalar split no longer clobbers @_ (RT #129297)
-----------------------------------------------------------------------
Summary of changes:
pod/perlsub.pod | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/pod/perlsub.pod b/pod/perlsub.pod
index f15f9ce..434bb8c 100644
--- a/pod/perlsub.pod
+++ b/pod/perlsub.pod
@@ -1582,14 +1582,14 @@ and someone has been calling it with an array or
expression
returning a list:
func(@foo);
- func( split /:/ );
+ func( $text =~ /\w+/g );
Then you've just supplied an automatic C<scalar> in front of their
argument, which can be more than a bit surprising. The old C<@foo>
which used to hold one thing doesn't get passed in. Instead,
C<func()> now gets passed in a C<1>; that is, the number of elements
-in C<@foo>. And the C<split> gets called in scalar context so it
-starts scribbling on your C<@_> parameter list. Ouch!
+in C<@foo>. And the C<m//g> gets called in scalar context so instead of a
+list of words it returns a boolean result and advances C<pos($text)>. Ouch!
If a sub has both a PROTO and a BLOCK, the prototype is not applied
until after the BLOCK is completely defined. This means that a recursive
--
Perl5 Master Repository
