Revision history for indirect
+0.14 2009-06-04 21:55 UTC
+ + Fix : Prevent bogus invalid syntaxes caused by reallocated memory
+ chunks. Thanks Andrew Main for reporting with a reproducible
+ test case.
+
0.13 2009-05-24 18:50 UTC
+ Add : The hook now receives the file name and the line where the
error happened in respectively $_[2] and $_[3].
--- #YAML:1.0
name: indirect
-version: 0.13
+version: 0.14
abstract: Lexically warn about using the indirect object syntax.
author:
- Vincent Pit <perl@profvince.com>
directory:
- t
- inc
-generated_by: ExtUtils::MakeMaker version 6.50
+generated_by: ExtUtils::MakeMaker version 6.52
meta-spec:
url: http://module-build.sourceforge.net/META-spec-v1.4.html
version: 1.4
indirect - Lexically warn about using the indirect object syntax.
VERSION
- Version 0.13
+ Version 0.14
SYNOPSIS
# In a script
turn it on by calling "no indirect"), this pragma warns about indirect
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 "sub" isn't defined, "sub $x" is actually
- interpreted as "$x->sub").
+ its use is error prone (when "swoosh" isn't defined, "swoosh $x"
+ actually compiles to "$x->swoosh").
It currently does not warn when the object is enclosed between braces
(like "meth { $obj } @args") or for core functions ("print" or "say").
True iff the module could have been built when thread-safety features.
CAVEATS
+ The implementation was tweaked to work around several limitations of
+ vanilla "perl" pragmas : it's thread safe, and doesn't 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").