From: Shawn M Moore <sartak@bestpractical.com>
Date: Tue, 6 Jul 2010 19:11:35 +0000 (-0400)
Subject: Move the MooseX:: namespace section under extending Moose
X-Git-Tag: 1.09~64
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=a94f30acea8d39caa544c9f87cc3200a46b82466;p=gitmo%2FMoose.git

Move the MooseX:: namespace section under extending Moose

    Doesn't really fit under metaclass compatibility
---

diff --git a/lib/Moose.pm b/lib/Moose.pm
index 0ba2a28..edfcfec 100644
--- a/lib/Moose.pm
+++ b/lib/Moose.pm
@@ -975,6 +975,16 @@ for you.
 
 An alias for C<confess>, used by internally by Moose.
 
+=head2 The MooseX:: namespace
+
+Generally if you're writing an extension I<for> Moose itself you'll want
+to put your extension in the C<MooseX::> namespace. This namespace is
+specifically for extensions that make Moose better or different in some
+fundamental way. It is traditionally B<not> for a package that just happens
+to use Moose. This namespace follows from the examples of the C<LWPx::>
+and C<DBIx::> namespaces that perform the same function for C<LWP> and C<DBI>
+respectively.
+
 =head1 METACLASS COMPATIBILITY AND MOOSE
 
 Metaclass compatibility is a thorny subject. You should start by
@@ -1002,16 +1012,6 @@ parent's and child's original metaclasses.
 Ultimately, this is all transparent to you except in the case of an
 unresolvable conflict.
 
-=head2 The MooseX:: namespace
-
-Generally if you're writing an extension I<for> Moose itself you'll want
-to put your extension in the C<MooseX::> namespace. This namespace is
-specifically for extensions that make Moose better or different in some
-fundamental way. It is traditionally B<not> for a package that just happens
-to use Moose. This namespace follows from the examples of the C<LWPx::>
-and C<DBIx::> namespaces that perform the same function for C<LWP> and C<DBI>
-respectively.
-
 =head1 CAVEATS
 
 =over 4