pjf: dual life modules
G'day Dave / p5p,
Attached is a patch that brings blead up to autodie 2.0, providing the new
hinting interface, and matching what's out there on the CPAN.
Cheerio,
Paul
--
Paul Fenwick <pjf@perltraining.com.au> | http://perltraining.com.au/
Director of Training | Ph: +61 3 9354 6001
Perl Training Australia | Fax: +61 3 9354 2681
From
41441253d22a31e4942ae0949102fada56b15343 Mon Sep 17 00:00:00 2001
From: Paul Fenwick <pjf@perltraining.com.au>
Date: Mon, 29 Jun 2009 12:08:21 +1000
Subject: [PATCH] Merge autodie 2.00 into CORE.
2.00 Mon Jun 29 01:24:49 AUSEST 2009
* FEATURE: autodie can now accept hints regarding how
user and module subroutines should be handled. See
autodie::hints for more information.
* INTERFACE: The calls to the internal subroutines
one_invocation() and write_invocation() have changed.
An additional argument (the user subroutine reference) is
passed as the second-last argument. This may break code
that previously tried to call these subroutines directly.
* BUGFIX: Calls to subroutines to File::Copy should now
correctly throw exceptions when called in a list context.
* BUGFIX: An internal error where autodie could potentially
fail to correctly report a dying function's name has been
fixed.
* BUGFIX: autodie will no longer clobber package scalars when
a format has the same name as an autodying function.
(Thanks to Ben Morrow)
* INTERFACE: The internal interfaces for fill_protos(),
one_invocation(), write_invocation() are now once again
backward compatible with legacy versions of Fatal. It is
still strongly recommended these interfaces are NOT called
directly. The _make_fatal() subroutine is not backwards
compatible.
* TEST: Added internal-backcompat.t to test backwards
compatibility of internal interfaces.
* DOCUMENTATION: Expanded documentation regarding how
autodie changes calls to system(), and how this must be
explicitly enabled.
* BUGFIX: A situation where certain compile-time diagnostics
and errors from autodie would not be displayed has been
fixed.
Signed-off-by: H.Merijn Brand <h.m.brand@xs4all.nl>