From: Dave Rolsky <autarch@urth.org>
Date: Sat, 11 Feb 2012 20:30:11 +0000 (-0600)
Subject: Rename Meta::Recipe5 to Meta::Table_MetaclassTrait
X-Git-Tag: 2.0500~63
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=826230c216b412742dc456ef9156559c2c9a62e0;p=gitmo%2FMoose.git

Rename Meta::Recipe5 to Meta::Table_MetaclassTrait
---

diff --git a/lib/Moose/Cookbook.pod b/lib/Moose/Cookbook.pod
index 2fe272d..e110b5d 100644
--- a/lib/Moose/Cookbook.pod
+++ b/lib/Moose/Cookbook.pod
@@ -127,7 +127,7 @@ functionality. However, attributes can only have one metaclass.
 Applying roles to the attribute metaclass lets you provide
 composable attribute functionality.
 
-=item L<Moose::Cookbook::Meta::Recipe5> - The "table" attribute implemented as a metaclass trait
+=item L<Moose::Cookbook::Meta::Table_MetaclassTrait>
 
 This recipe takes the class metaclass we saw in the previous recipe
 and reimplements it as a metaclass trait.
diff --git a/lib/Moose/Cookbook/Extending/Recipe1.pod b/lib/Moose/Cookbook/Extending/Recipe1.pod
index c4d41c6..35d8ec9 100644
--- a/lib/Moose/Cookbook/Extending/Recipe1.pod
+++ b/lib/Moose/Cookbook/Extending/Recipe1.pod
@@ -39,7 +39,7 @@ a few broad categories.
 =head2 Metaclass Extensions
 
 One way of extending Moose is by extending one or more Moose
-metaclasses. For example, in L<Moose::Cookbook::Meta::Recipe5> we saw
+metaclasses. For example, in L<Moose::Cookbook::Meta::Table_MetaclassTrait> we saw
 a metaclass role that added a C<table> attribute to the
 metaclass. If you were writing an ORM, this would be a logical
 extension.
@@ -120,8 +120,8 @@ can refer to it by a short name like "Big", and Moose will resolve it to a
 class like C<MooseX::Embiggen::Meta::Attribute::Role::Big>.
 
 See L<Moose::Cookbook::Meta::Labeled_AttributeTrait> and
-L<Moose::Cookbook::Meta::Recipe5> for examples of traits in action. In
-particular, both of these recipes demonstrate the trait resolution
+L<Moose::Cookbook::Meta::Table_MetaclassTrait> for examples of traits in
+action. In particular, both of these recipes demonstrate the trait resolution
 mechanism.
 
 Implementing an extension as a (set of) metaclass or base object
diff --git a/lib/Moose/Cookbook/Extending/Recipe4.pod b/lib/Moose/Cookbook/Extending/Recipe4.pod
index a716106..0509279 100644
--- a/lib/Moose/Cookbook/Extending/Recipe4.pod
+++ b/lib/Moose/Cookbook/Extending/Recipe4.pod
@@ -37,8 +37,8 @@ __END__
 
 This recipe expands on the use of L<Moose::Exporter> we saw in
 L<Moose::Cookbook::Extending::Recipe1> and the class metaclass trait we saw in
-L<Moose::Cookbook::Meta::Recipe5>. In this example we provide our own
-metaclass trait, and we also export a C<has_table> sugar function.
+L<Moose::Cookbook::Meta::Table_MetaclassTrait>. In this example we provide our
+own metaclass trait, and we also export a C<has_table> sugar function.
 
 The C<with_meta> parameter specifies a list of functions that should
 be wrapped before exporting. The wrapper simply ensures that the
diff --git a/lib/Moose/Cookbook/Meta/Recipe5.pod b/lib/Moose/Cookbook/Meta/Table_MetaclassTrait.pod
similarity index 97%
rename from lib/Moose/Cookbook/Meta/Recipe5.pod
rename to lib/Moose/Cookbook/Meta/Table_MetaclassTrait.pod
index 54f5c56..1618947 100644
--- a/lib/Moose/Cookbook/Meta/Recipe5.pod
+++ b/lib/Moose/Cookbook/Meta/Table_MetaclassTrait.pod
@@ -1,4 +1,4 @@
-package Moose::Cookbook::Meta::Recipe5;
+package Moose::Cookbook::Meta::Table_MetaclassTrait;
 
 # ABSTRACT: Adding a "table" attribute as a metaclass trait