+0.31 2013-09-05 16:45 UTC
+ + Fix : [RT #88428] : no indirect in eval can trigger for direct calls
+ on __PACKAGE__
+ Thanks Graham Knop for reporting.
+ + Tst : Author tests are no longer bundled with this distribution.
+ They are only made available to authors in the git repository.
+
+0.30 2013-05-16 15:55 UTC
+ + Fix : [RT #83806] : false positives with Devel::Declare
+ [RT #83839] : false positive using ? : syntax
+ Thanks Andrew Main for the patch.
+ However, please note that the reason this patch seems to fix
+ thinks has not been explained.
+ + Fix : [RT #84649] : incorrect RT link in metadata
+ Thanks Karen Etheridge for reporting.
+
+0.29 2013-03-05 01:30 UTC
+ + Fix : [RT #83659] : false positives
+ Proper method calls in string-like environments (like
+ "@{[ $x->new ]}" will no longer be reported as indirect.
+ This was a regression in 0.28.
+ Thanks Andrew Main for reporting.
+ + Fix : Broken linkage on Windows with gcc 3.4, which appears in
+ particular when using ActivePerl's default compiler suite.
+ For those setups, the indirect shared library will now be
+ linked against the perl dll directly (instead of the import
+ library).
+
+0.28 2013-02-26 17:05 UTC
+ + Fix : [RT #83450] : newlines confuse indirect
+ Perl sometimes resets the line buffer between the object and
+ the method name (e.g. for "sort Class\n->method" outside of
+ eval), and this could cause direct method calls to be reported
+ as indirect.
+ Thanks Gianni Ceccarelli for reporting.
+ + Fix : Check functions are now replaced and restored in a thread-safe
+ manner, either by using the wrap_op_checker() function from perl
+ when it is available (starting from perl 5.16) or by taking the
+ OP_REFCNT mutex on older perls.
+
+0.27 2013-01-30 19:00 UTC
+ + Fix : [RT #82562] : indirect/Devel::CallParser interaction
+ indirect has been taught to play nicely with Devel::CallParser.
+ Thanks Andrew Main for the patch.
+ + Tst : Author tests overhaul.
+
+0.26 2011-10-23 14:25 UTC
+ + Add : "no indirect 'global'" enables the pragma for the whole program,
+ except for lexical scopes that "use indirect" explicitely.
+ + Chg : Passing both the 'fatal' and 'hook' options to unimport() is
+ now considered an error, and will result in an exception.
+ unimport() used to consider only the first passed option of
+ those two, and silently ignored the other.
+ + Tst : Test failures of t/41-threads-teardown.t and t/50-external.t on
+ Cygwin should have been addressed.
+ + Tst : Threads tests will not fail anymore if resources constraints
+ prevent the system from creating all the required threads.
+
+0.25 2011-08-24 15:40 UTC
+ + Fix : RT #69291 is now also fixed for perl 5.8. The pragma will no
+ longer vivify the "indirect" entry in the hints hash %^H on
+ perl 5.8.
+ + Tst : Attempt to make t/50-external.t pass on Cygwin.
+
+0.24 2011-07-17 23:15 UTC
+ + Fix : [RT #64521] : "no indirect" leaking into eval.
+ This is currently only fixed for perl 5.10 (perl 5.12 and
+ higher were never affected). It was caused by a very stupid
+ mistake of mine that was introduced in indirect version 0.23.
+ Thanks Michael G Schwern for reporting.
+ + Fix : [RT #69291] : indirect.pm breaks %^H.
+ This was caused by the same mistake as for the previous bug,
+ and as such it is also only fixed for perl 5.10 (and never
+ affected perl 5.12).
+ Thanks Andrew Main for reporting.
+ + Doc : C++ compilers are officially NOT supported.
+
+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 "${\( ... )}", "@{[ ... ]}",
+ 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.
+