more complete File::Spec support for Mac and VMS, tests (from

[p5sagit/p5-mst-13.2.git] / lib / strict.pm

diff --git a/lib/strict.pm b/lib/strict.pm
index 940e8bf..f9d60af 100644 (file)
--- a/lib/strict.pm
+++ b/lib/strict.pm
@@ -38,8 +38,8 @@ use symbolic references (see L<perlref>).
 =item C<strict vars>
 
 This generates a compile-time error if you access a variable that wasn't
-declared via C<use vars>,
-localized via C<my()> or wasn't fully qualified.  Because this is to avoid
+declared via "our" or C<use vars>,
+localized via C<my()>, or wasn't fully qualified.  Because this is to avoid
 variable suicide problems and subtle dynamic scoping issues, a merely
 local() variable isn't good enough.  See L<perlfunc/my> and
 L<perlfunc/local>.
@@ -50,12 +50,15 @@ L<perlfunc/local>.
     local $foo = 9;     # blows up
 
     package Cinna;
-    use vars qw/ $bar /;       # Declares $bar in current package
+    our $bar;                  # Declares $bar in current package
     $bar = 'HgS';              # ok, global declared via pragma
 
 The local() generated a compile-time error because you just touched a global
 name without fully qualifying it.
 
+Because of their special use by sort(), the variables $a and $b are
+exempted from this check.
+
 =item C<strict subs>
 
 This disables the poetry optimization, generating a compile-time error if