summaryrefslogtreecommitdiff
path: root/pod/perlsub.pod
diff options
context:
space:
mode:
authorRicardo Signes <rjbs@cpan.org>2015-10-06 15:42:05 -0400
committerRicardo Signes <rjbs@cpan.org>2015-10-06 15:42:05 -0400
commit55121b6b0516ee559126c7bee6b4b43b1e8f59f7 (patch)
tree69dde985d591581f90678ca06fbe476326dbbc69 /pod/perlsub.pod
parent15ca59302b4ab8afbcc002f9d3d491cf93143e7a (diff)
downloadperl-55121b6b0516ee559126c7bee6b4b43b1e8f59f7.tar.gz
perlsub.pod: note that anonymous subs can have signatures, too
Diffstat (limited to 'pod/perlsub.pod')
-rw-r--r--pod/perlsub.pod3
1 files changed, 2 insertions, 1 deletions
diff --git a/pod/perlsub.pod b/pod/perlsub.pod
index 4a3e6fd3a3..78de284733 100644
--- a/pod/perlsub.pod
+++ b/pod/perlsub.pod
@@ -319,7 +319,8 @@ disabled.
The signature is part of a subroutine's body. Normally the body of a
subroutine is simply a braced block of code. When using a signature,
the signature is a parenthesised list that goes immediately after
-the subroutine name. The signature declares lexical variables that are
+the subroutine name (or, for anonymous subroutines, immediately after
+the C<sub> keyword). The signature declares lexical variables that are
in scope for the block. When the subroutine is called, the signature
takes control first. It populates the signature variables from the
list of arguments that were passed. If the argument list doesn't meet