+ As explained in "unimport"'s description, an "use indirect" statement
+ will lexically override a global policy previously installed by "no
+ indirect 'global', ..." (if there's one).
+
+FUNCTIONS
+ "msg"
+ my $msg = msg($object, $method, $file, $line);
+
+ Returns the default error message that "indirect" generates when an
+ indirect method call is reported.
+
+CONSTANTS
+ "I_THREADSAFE"
+ True iff the module could have been built with thread-safety features
+ enabled.
+
+ "I_FORKSAFE"
+ True iff this module could have been built with fork-safety features
+ enabled. This will always be true except on Windows where it's false for
+ perl 5.10.0 and below .
+
+DIAGNOSTICS
+ "Indirect call of method "%s" on object "%s" at %s line %d."
+ The default warning/exception message thrown when an indirect method
+ call on an object is found.
+
+ "Indirect call of method "%s" on a block at %s line %d."
+ The default warning/exception message thrown when an indirect method
+ call on a block is found.
+
+ENVIRONMENT
+ "PERL_INDIRECT_PM_DISABLE"
+ If this environment variable is set to true when the pragma is used for
+ the first time, the XS code won't be loaded and, although the 'indirect'
+ lexical hint will be set to true in the scope of use, the pragma itself
+ won't do anything. In this case, the pragma will always be considered to
+ be thread-safe, and as such "I_THREADSAFE" will be true. This is useful
+ for disabling "indirect" in production environments.
+
+ Note that clearing this variable after "indirect" was loaded has no
+ 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 does not suffer from a
+ "perl 5.8.x-5.10.0" bug that causes all pragmas to propagate into
+ "require"d scopes.
+
+ Before "perl" 5.12, "meth $obj" (no semicolon) at the end of a file is
+ not seen as an indirect method call, 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
+ addressed in perl 5.10.
+
+ The search for indirect method calls happens before constant folding.
+ Hence "my $x = new Class if 0" will be caught.
+
+REFERENCES
+ Numerous articles have been written about the quirks of the indirect
+ object construct :
+
+ * <http://markmail.org/message/o7d5sxnydya7bwvv> : Far More Than
+ Everything You've Ever Wanted to Know about the Indirect Object
+ syntax, Tom Christiansen, 1998-01-28.
+
+ This historical post to the "perl5-porters" mailing list raised
+ awareness about the perils of this syntax.
+
+ * <http://www.shadowcat.co.uk/blog/matt-s-trout/indirect-but-still-fat
+ al> : Indirect but still fatal, Matt S. Trout, 2009-07-29.
+
+ In this blog post, the author gives an example of an undesirable
+ indirect method call on a block that causes a particularly
+ bewildering error.
+