Revision history for indirect
+0.23 2010-10-03 00:15 UTC
+ + Fix : Some indirect constructs could be incorrectly reported when
+ several modules were used in the same scope. This caused
+ t/30-scope.t to fail randomly.
+ + Tst : Threads tests are now only run on perl 5.13.4 and higher.
+ They could segfault randomly because of what seems to be an
+ internal bug of Perl, which has been addressed in 5.13.4.
+ There is also an environment variable that allows you to
+ forcefully run those tests, but it should be set only for
+ author testing and not for end users.
+
0.22 2010-08-16 16:00 UTC
+ Add : Indirect constructs are now reported for code interpolated
in quote-like environments, like "${\( ... )}", "@{[ ... ]}",
indirect - Lexically warn about using the indirect object syntax.
VERSION
- Version 0.22
+ Version 0.23
SYNOPSIS
# In a script
"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