X-Git-Url: http://git.vpit.fr/?p=perl%2Fmodules%2Findirect.git;a=blobdiff_plain;f=README;h=e1aa30551a21b8d57b5b484bfd0709930de61adc;hp=a563ea0adc3a9a95c73022856fa910878e409c71;hb=485841aab90380ffecbe0f217eb234a64f69bb25;hpb=e3cc63669e7d84f338348281f313709bae0be8af

diff --git a/README b/README
index a563ea0..e1aa305 100644
--- a/README
+++ b/README
@@ -2,7 +2,7 @@ NAME
     indirect - Lexically warn about using the indirect object syntax.
 
 VERSION
-    Version 0.21
+    Version 0.23
 
 SYNOPSIS
         # In a script
@@ -18,7 +18,7 @@ SYNOPSIS
         }
         try { ... }; # warns
 
-        no indirect ':fatal';
+        no indirect ':fatal';    # or 'FATAL', or ':Fatal' ...
         if (defied $foo) { ... } # croaks, note the typo
 
         # From the command-line
@@ -34,7 +34,7 @@ DESCRIPTION
     object syntax constructs that may have slipped into your code.
 
     This syntax is now considered harmful, since its parsing has many quirks
-    and its use is error prone (when "swoosh" isn't defined, "swoosh $x"
+    and its use is error prone (when "swoosh" is not defined, "swoosh $x"
     actually compiles to "$x->swoosh"). In
     <http://www.shadowcat.co.uk/blog/matt-s-trout/indirect-but-still-fatal>,
     Matt S. Trout gives an example of an indirect construct that can cause a
@@ -47,12 +47,12 @@ DESCRIPTION
     This module is not a source filter.
 
 METHODS
-  "unimport [ hook => $hook | ':fatal' ]"
+  "unimport [ hook => $hook | ':fatal', 'FATAL', ... ]"
     Magically called when "no indirect @opts" is encountered. Turns the
     module on. The policy to apply depends on what is first found in @opts :
 
-    *   If it's the string ':fatal', the compilation will croak on the first
-        indirect syntax met.
+    *   If it is a string that matches "/^:?fatal$/i", the compilation will
+        croak on the first indirect syntax met.
 
     *   If the key/value pair "hook => $hook" comes first, $hook will be
         called for each error with a string representation of the object as
@@ -99,18 +99,20 @@ ENVIRONMENT
     for disabling "indirect" in production environments.
 
     Note that clearing this variable after "indirect" was loaded has no
-    effect. If you want to reenable the pragma later, you also need to
+    effect. If you want to re-enable the pragma later, you also need to
     reload it by deleting the 'indirect.pm' entry from %INC.
 
 CAVEATS
     The implementation was tweaked to work around several limitations of
-    vanilla "perl" pragmas : it's thread safe, and doesn't suffer from a
+    vanilla "perl" pragmas : it's thread safe, and does not suffer from a
     "perl 5.8.x-5.10.0" bug that causes all pragmas to propagate into
     "require"d scopes.
 
-    "meth $obj" (no semicolon) at the end of a file won't be seen as an
-    indirect object syntax, although it will as soon as there is another
-    token before the end (as in "meth $obj;" or "meth $obj 1").
+    Before "perl" 5.12, "meth $obj" (no semicolon) at the end of a file is
+    not seen as an indirect object syntax, although it is as soon as there
+    is another token before the end (as in "meth $obj;" or "meth $obj 1").
+    If you use "perl" 5.12 or greater, those constructs are correctly
+    reported.
 
     With 5.8 perls, the pragma does not propagate into "eval STRING". This
     is due to a shortcoming in the way perl handles the hints hash, which is