summaryrefslogtreecommitdiff
path: root/pod
diff options
context:
space:
mode:
authorDavid Golden <dagolden@cpan.org>2012-07-05 20:14:15 -0400
committerDavid Golden <dagolden@cpan.org>2012-07-05 20:14:15 -0400
commit848bab4facdb0e4d55df87ebb5078741d248bb2b (patch)
tree0f4e47ff68ef8c4de5fc64751151b8e19d3a7e3d /pod
parent4dd9551803b40a514a28062780b164fdfbb4ef59 (diff)
downloadperl-848bab4facdb0e4d55df87ebb5078741d248bb2b.tar.gz
perlfunc: clarify 'our' again for vars.pm behavior
rjbs discovered that vars.pm docs lie and it works within a package, even across file scopes
Diffstat (limited to 'pod')
-rw-r--r--pod/perlfunc.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/pod/perlfunc.pod b/pod/perlfunc.pod
index 2d730996bb..8e8bccaa25 100644
--- a/pod/perlfunc.pod
+++ b/pod/perlfunc.pod
@@ -4279,8 +4279,8 @@ allocate storage for that name within the current scope.
This means that when C<use strict 'vars'> is in effect, C<our> lets you use
a package variable without qualifying it with the package name, but only within
the lexical scope of the C<our> declaration. In this way, C<our> differs from
-C<use vars>, which allows a the use of an unqualified name I<only> within the
-affected package.
+C<use vars>, which allows use of an unqualified name I<only> within the
+affected package, but across scopes.
If more than one value is listed, the list must be placed
in parentheses.