File::Spec 0.82 beta

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

diff --git a/lib/strict.pm b/lib/strict.pm
index 99ed01d..042227f 100644 (file)
--- a/lib/strict.pm
+++ b/lib/strict.pm
@@ -34,12 +34,14 @@ use symbolic references (see L<perlref>).
     print $$ref;       # ok
     $ref = "foo";
     print $$ref;       # runtime error; normally ok
+    $file = "STDOUT";
+    print $file "Hi!"; # error; note: no comma after $file
 
 =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,7 +52,7 @@ 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