From: Dave Rolsky <autarch@urth.org>
Date: Thu, 11 Dec 2008 03:45:08 +0000 (+0000)
Subject: Move mention of ->meta later in the docs
X-Git-Tag: 0.66~27^2~40
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=056348be7913c8c706c2837ff4731bcc17afa14a;p=gitmo%2FMoose.git

Move mention of ->meta later in the docs
---

diff --git a/lib/Moose/Manual/Classes.pod b/lib/Moose/Manual/Classes.pod
index b4081ae..35af4cf 100644
--- a/lib/Moose/Manual/Classes.pod
+++ b/lib/Moose/Manual/Classes.pod
@@ -34,10 +34,6 @@ documentation.
 Loading Moose in your class also turns on the C<strict> and
 C<warnings> pragmas in your class for you.
 
-It also creates a L<Moose::Meta::Class> object for your class. This
-metaclass object is now available by calling a C<meta> method on your
-class, for example C<< Person->meta >>.
-
 The metaclass object an introspection API for your class. It is also
 used by Moose itself under the hood to add attributes, define parent
 classes, and so on. In fact, all of Moose's sugar does the real work
@@ -55,6 +51,10 @@ class, by calling the C<class_type> function in
 L<Moose::Util::Constraints>. See the L<Moose::Manual::Types> document
 for more about types.
 
+It also creates a L<Moose::Meta::Class> object for your class. This
+metaclass object is now available by calling a C<meta> method on your
+class, for example C<< Person->meta >>.
+
 =head1 SUBCLASSING
 
 Moose provides a simple sugar function for declaring your parent