diff options
| author | Christian Winter <bitpoet@linux-config.de> | 2007-04-01 20:01:24 +0200 |
|---|---|---|
| committer | Rafael Garcia-Suarez <rgarciasuarez@gmail.com> | 2007-04-02 08:50:23 +0000 |
| commit | 73c71df6a9051c0d8926b8aae2d513c596501d60 (patch) | |
| tree | 68f3055973a3aad704a517234b9c5827def4db38 /pod/perlfunc.pod | |
| parent | 08322f8f31e7d47b6c567249e73bacf200f45f3d (diff) | |
| download | perl-73c71df6a9051c0d8926b8aae2d513c596501d60.tar.gz | |
perlfunc.pod: Lexical visibility hint in require docu
Message-ID: <460FD754.8050106@linux-config.de>
p4raw-id: //depot/perl@30828
Diffstat (limited to 'pod/perlfunc.pod')
| -rw-r--r-- | pod/perlfunc.pod | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod index 1395631c15..eb6bd57794 100644 --- a/pod/perlfunc.pod +++ b/pod/perlfunc.pod @@ -4467,8 +4467,9 @@ version should be used instead. Otherwise, C<require> demands that a library file be included if it hasn't already been included. The file is included via the do-FILE -mechanism, which is essentially just a variety of C<eval>. Has -semantics similar to the following subroutine: +mechanism, which is essentially just a variety of C<eval> with the +caveat that lexical variables in the invoking script will be invisible +to the included code. Has semantics similar to the following subroutine: sub require { my ($filename) = @_; |