From: Chris Prather <chris@prather.org>
Date: Sun, 12 Oct 2008 20:46:38 +0000 (+0000)
Subject: doc patch to explain MooseX:: namespace
X-Git-Tag: 0.59~10
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=fafec530033f11e06254e679be7e3910f5881095;p=gitmo%2FMoose.git

doc patch to explain MooseX:: namespace
---

diff --git a/lib/Moose.pm b/lib/Moose.pm
index e792bb1..e971009 100644
--- a/lib/Moose.pm
+++ b/lib/Moose.pm
@@ -938,6 +938,16 @@ 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