1.11 Apr 12, 2004
- No code changes, just switching to including a Makefile.PL that uses
ExtUtils::MakeMaker instead of one that sneakily uses Module::Build.
Requested by Perrin Harkins.
1.10 Mar 10, 2004
- Silence a warning from the test code if Exception::Class isn't
installed. Reported by Stefano Ruberti.
- Localize $@ to avoid overwriting a previously set $@ while creating
a Devel::StackTrace object. This caused a test failure in the
Exception::Class tests when run with Perl 5.6.1, but not with 5.8.3.
I don't really know how to test for it outside of Exception::Class.
Reported by Jesse Erlbaum.
1.09 Feb 26, 2004
- The overload workaround blows up if a DBI handle is anywhere in the
stack, because of a bad interaction between overload::Overloaded and
DBI's custom dispatching. This release works around that.
1.08 Feb 23, 2004
- Some tests failed on Win32 because they were hardcoded to expect a
file name with forward slashes. Reported by Steve Hay.
1.07 Feb 21, 2004
- This release includes a change to the overload handling that is
necessary for cooperation with Exception::Class.
1.06 Feb 21, 2004
- Devel::StackTrace now uses overload::StrVal() to get the underlying
string value of an overloaded object when creating a stack frame for
display. This can be turned off by setting respect_overload to a true
value. Suggested by Matt Sisk.
1.05 Feb 17, 2004
- Devel::StackTrace incorrectly reported that arguments were being
passed to eval blocks (which isn't possible). Reported by Mark Dedlow.
1.04 Sep 25, 2003
- The special handling of Exception::Class::Base objects was broken.
This was exposed by the fact that Exception::Class 1.15 now uses
Devel::StackTrace in a slightly different way than it did previously.
1.03 Jan 22, 2003
- Special handling of Exception::Class::Base objects when stringifying
references. This avoids infinite recursion between the two classes.
Requested by p5-Exception-Class package (hi he!).
The Devel::StackTrace module contains two classes, Devel::StackTrace and
Devel::StackTraceFrame. The goal of this object is to encapsulate the
information that can found through using the caller() function, as well
as providing a simple interface to this data.
