X-Git-Url: http://git.vpit.fr/?a=blobdiff_plain;f=README;h=81143158bd691e500cf27f758b88cdc2b3254a24;hb=192a2eab8d6e0ba5d0f021eb8339a59df18577e7;hp=a60c8d7308aeb6909571e6ca75aa01b3c97774e7;hpb=c2e8dfbf550e0a15ff415a698c806e1fc8ca03fe;p=perl%2Fmodules%2FPerl-Critic-Policy-Dynamic-NoIndirect.git

diff --git a/README b/README
index a60c8d7..8114315 100644
--- a/README
+++ b/README
@@ -3,7 +3,7 @@ NAME
     indirect method calls.
 
 VERSION
-    Version 0.01
+    Version 0.04
 
 DESCRIPTION
     This Perl::Critic dynamic policy reports any use of indirect object
@@ -13,6 +13,19 @@ DESCRIPTION
     Since it wraps around indirect, it needs to compile the audited code and
     as such is implemented as a subclass of Perl::Critic::DynamicPolicy.
 
+CAVEATS
+    The uses of the indirect pragma inside the auditted code take precedence
+    over this policy. Hence no violations will be reported for indirect
+    method calls that are located inside the lexical scope of "use indirect"
+    or "no indirect hook => ...". Occurrences of "no indirect" won't be a
+    problem.
+
+    Since the reports generated by indirect are remapped to the
+    corresponding PPI::Element objects, the order in which the violations
+    are returned is different from the order given by indirect : the former
+    is the document order (top to bottom, left to right) while the latter is
+    the optree order (arguments before function calls).
+
 DEPENDENCIES
     perl 5.8, Carp.