diff options
| author | Mark-Jason Dominus <mjd@plover.com> | 1999-01-16 12:22:06 -0500 |
|---|---|---|
| committer | Jarkko Hietaniemi <jhi@iki.fi> | 1999-02-02 16:09:03 +0000 |
| commit | 4536e65df88825e8caa0a99c75b5c7283dc3c2ec (patch) | |
| tree | 7c2be87787f9670a07962e717b6bf505c87feb82 /pod/perlsub.pod | |
| parent | 23ad5bf58812d09778a31055c1c5386b41da6ac2 (diff) | |
| download | perl-4536e65df88825e8caa0a99c75b5c7283dc3c2ec.tar.gz | |
Re: DOC PATCH (5.005_54 perlsub.pod)
Message-ID: <19990116222206.3674.qmail@plover.com>
p4raw-id: //depot/cfgperl@2785
Diffstat (limited to 'pod/perlsub.pod')
| -rw-r--r-- | pod/perlsub.pod | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/pod/perlsub.pod b/pod/perlsub.pod index 95fbb6b342..6f9bb7fcd5 100644 --- a/pod/perlsub.pod +++ b/pod/perlsub.pod @@ -825,7 +825,8 @@ if you call it like a builtin function, then it behaves like a builtin function. If you call it like an old-fashioned subroutine, then it behaves like an old-fashioned subroutine. It naturally falls out from this rule that prototypes have no influence on subroutine references -like C<\&foo> or on indirect subroutine calls like C<&{$subref}>. +like C<\&foo> or on indirect subroutine calls like C<&{$subref}> or +C<$subref-E<gt>()>. Method calls are not influenced by prototypes either, because the function to be called is indeterminate at compile time, because it depends |