Revision history for indirect
+0.22 2010-08-16 16:00 UTC
+ + Add : Indirect constructs are now reported for code interpolated
+ in quote-like environments, like "${\( ... )}", "@{[ ... ]}",
+ s/pattern/ ... /e, qr/(?{ ... })/ or qr/(??{ ... })/.
+ + Add : You can now make the pragma lethal by passing anything matching
+ /^:?fatal$/i to import(), including "FATAL" and ":Fatal".
+ + Fix : [RT #60378] : segmentation fault on indirect_ck_method.
+ This caused constructs like "@{[ $obj->$meth ]}" to segfault
+ when $meth was a lexical.
+ Thanks Tokuhiro Matsuno for reporting.
+
0.21 2010-05-31 23:10 UTC
+ Chg : perl 5.8.1 is now required (instead of 5.8.0).
+ Fix : [RT #57699] : indirect fail with 64-bit int on 5.13.1.
indirect - Lexically warn about using the indirect object syntax.
VERSION
- Version 0.21
+ Version 0.22
SYNOPSIS
# In a script
}
try { ... }; # warns
- no indirect ':fatal';
+ no indirect ':fatal'; # or 'FATAL', or ':Fatal' ...
if (defied $foo) { ... } # croaks, note the typo
# From the command-line
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
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
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.