overriding new isn't necessary when using mx-nonmoose

[gitmo/Moose.git] / lib / Moose / Cookbook / Basics / Recipe11.pod

diff --git a/lib/Moose/Cookbook/Basics/Recipe11.pod b/lib/Moose/Cookbook/Basics/Recipe11.pod
index 932bf99..e64902e 100644 (file)
--- a/lib/Moose/Cookbook/Basics/Recipe11.pod
+++ b/lib/Moose/Cookbook/Basics/Recipe11.pod
@@ -35,17 +35,6 @@ use Test::Requires {
       predicate => 'has_mayan_date',
   );
 
-  sub new {
-      my $class = shift;
-
-      my $obj = $class->SUPER::new(@_);
-
-      return $class->meta->new_object(
-          __INSTANCE__ => $obj,
-          @_,
-      );
-  }
-
   after 'set' => sub {
       $_[0]->_clear_mayan_date;
   };
@@ -59,7 +48,7 @@ use Test::Requires {
 This recipe demonstrates how to use Moose to subclass a parent which
 is not Moose based. This recipe only works if the parent class uses a
 blessed hash reference for object instances. If your parent is doing
-something funkier, you should check out L<MooseX::InsideOut>.
+something funkier, you should check out L<MooseX::NonMoose::InsideOut> and L<MooseX::InsideOut>.
 
 The meat of this recipe is contained in L<MooseX::NonMoose>, which does all
 the grunt work for you.