From: Jesse Luehrs <doy@tozt.net>
Date: Mon, 20 Feb 2012 14:07:37 +0000 (-0600)
Subject: class metaclasses can also be applied directly
X-Git-Tag: 2.0500~49
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=59828e5f89d6e3119fd07e0aee751a832abdb971;p=gitmo%2FMoose.git

class metaclasses can also be applied directly
---

diff --git a/lib/Moose/Cookbook/Extending/ExtensionOverview.pod b/lib/Moose/Cookbook/Extending/ExtensionOverview.pod
index 8ca876f..05f10df 100644
--- a/lib/Moose/Cookbook/Extending/ExtensionOverview.pod
+++ b/lib/Moose/Cookbook/Extending/ExtensionOverview.pod
@@ -235,9 +235,10 @@ B<Note: We strongly recommend that you provide your extension as a set of
 roles whenever possible>.
 
 Moose does not provide any simple APIs for consumers to use a subclass
-extension, except for attribute metaclasses. The attribute declaration
-options include a C<metaclass> option a consumer of your extension can
-use to specify your subclass.
+extension, except for class and attribute metaclasses. The attribute
+declaration options include a C<metaclass> option a consumer of your extension
+can use to specify your subclass, and class metaclasses can be passed via the
+C<-metaclass> import option when you C<use Moose>.
 
 This is one reason why implementing an extension as a subclass can be
 a poor choice. However, you can force the use of certain subclasses at