From: Jesse Luehrs <doy@tozt.net>
Date: Mon, 20 Feb 2012 14:06:18 +0000 (-0600)
Subject: add another warning against subclass extensions
X-Git-Tag: 2.0500~50
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=e32cc90689604524860bdb57415287d149a7a4db;p=gitmo%2FMoose.git

add another warning against subclass extensions
---

diff --git a/lib/Moose/Cookbook/Extending/ExtensionOverview.pod b/lib/Moose/Cookbook/Extending/ExtensionOverview.pod
index 764e504..8ca876f 100644
--- a/lib/Moose/Cookbook/Extending/ExtensionOverview.pod
+++ b/lib/Moose/Cookbook/Extending/ExtensionOverview.pod
@@ -274,6 +274,14 @@ subclasses:
       );
   }
 
+Note that there are several issues with this sort of extension mechanism, most
+notably that Moose only ever initializes the metaclass for a class once. This
+means that this extension must be loaded B<first>, before anything
+Moose-related touches the class. If you say C<use Moose; use
+MooseX::Embiggen;>, for instance, the extension will not be applied properly.
+There are very few reasons to implement an extension in this way; using
+metaclass traits is the right answer in nearly every case.
+
 =head1 LEGACY EXTENSION MECHANISMS
 
 Before the existence of L<Moose::Exporter> and