Workaround for double-call of destructors (based on 3d56e026 and e1d9e578)

[dbsrgits/DBIx-Class.git] / lib / DBIx / Class.pm

diff --git a/lib/DBIx/Class.pm b/lib/DBIx/Class.pm
index a6964fd..b7f24ee 100644 (file)
--- a/lib/DBIx/Class.pm
+++ b/lib/DBIx/Class.pm
@@ -11,7 +11,7 @@ our $VERSION;
 # $VERSION declaration must stay up here, ahead of any other package
 # declarations, as to not confuse various modules attempting to determine
 # this ones version, whether that be s.c.o. or Module::Metadata, etc
-$VERSION = '0.082700_06';
+$VERSION = '0.082899_01';
 
 $VERSION = eval $VERSION if $VERSION =~ /_/; # numify for warning-free dev releases
 
@@ -27,6 +27,13 @@ use DBIx::Class::Exception;
 __PACKAGE__->mk_group_accessors(inherited => '_skip_namespace_frames');
 __PACKAGE__->_skip_namespace_frames('^DBIx::Class|^SQL::Abstract|^Try::Tiny|^Class::Accessor::Grouped|^Context::Preserve');
 
+# FIXME - this is not really necessary, and is in
+# fact going to slow things down a bit
+# However it is the right thing to do in order to get
+# various install bases to highlight their brokenness
+# Remove at some unknown point in the future
+sub DESTROY { &DBIx::Class::_Util::detected_reinvoked_destructor }
+
 sub mk_classdata {
   shift->mk_classaccessor(@_);
 }
@@ -306,13 +313,13 @@ The fine folks nudging the project in a particular direction:
 
 =over
 
-ribasushi: Peter Rabbitson <ribasushi@cpan.org>
+B<ribasushi>: Peter Rabbitson <ribasushi@cpan.org>
 (present day maintenance and controlled evolution)
 
-castaway: Jess Robinson <castaway@desert-island.me.uk>
+B<castaway>: Jess Robinson <castaway@desert-island.me.uk>
 (lions share of the reference documentation and manuals)
 
-mst: Matt S Trout <mst@shadowcat.co.uk> (project founder -
+B<mst>: Matt S Trout <mst@shadowcat.co.uk> (project founder -
 original idea, architecture and implementation)
 
 =back