summaryrefslogtreecommitdiff
path: root/pod/perlsub.pod
diff options
context:
space:
mode:
authorRicardo Signes <rjbs@cpan.org>2016-04-23 11:50:24 +0100
committerRicardo Signes <rjbs@cpan.org>2016-04-23 11:50:24 +0100
commit8c13e94604b1db7743f11c459b95a61238963cc8 (patch)
tree2da9af813ddacf66be2ed8ac1301ad45da4724d7 /pod/perlsub.pod
parenta95b3d6ada665e29ff33e3063306726e5ec40338 (diff)
downloadperl-8c13e94604b1db7743f11c459b95a61238963cc8.tar.gz
Revert "document that sigs in future may not populate @_"
This reverts commit 19d6c3854e96d89bf4dc2d874df433beac27ee8b.
Diffstat (limited to 'pod/perlsub.pod')
-rw-r--r--pod/perlsub.pod8
1 files changed, 3 insertions, 5 deletions
diff --git a/pod/perlsub.pod b/pod/perlsub.pod
index a7b9bf3642..78de284733 100644
--- a/pod/perlsub.pod
+++ b/pod/perlsub.pod
@@ -458,11 +458,9 @@ that the caller passed no arguments:
return 123;
}
-When using a signature, the arguments are currently still available in the
-special array variable C<@_>, in addition to the lexical variables of the
-signature, but in a future release of perl that may change to being not
-available by default. There is a difference between the two ways of
-accessing the
+When using a signature, the arguments are still available in the special
+array variable C<@_>, in addition to the lexical variables of the
+signature. There is a difference between the two ways of accessing the
arguments: C<@_> I<aliases> the arguments, but the signature variables
get I<copies> of the arguments. So writing to a signature variable
only changes that variable, and has no effect on the caller's variables,