Restore deleted recipes under Moose::Cookbook::Legacy

[gitmo/Moose.git] / lib / Moose / Cookbook.pod

diff --git a/lib/Moose/Cookbook.pod b/lib/Moose/Cookbook.pod
index 511f155..53448a7 100644 (file)
--- a/lib/Moose/Cookbook.pod
+++ b/lib/Moose/Cookbook.pod
@@ -120,30 +120,33 @@ you extend the object system provided by Moose.
 If you're wondering what all this "meta" stuff is, and why you should
 care about it, read this "recipe".
 
-=item L<Moose::Cookbook::Meta::Recipe3> - Labels implemented via attribute traits
+=item L<Moose::Cookbook::Meta::Labeled_AttributeTrait>
 
 Extending Moose's attribute metaclass is a great way to add
 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.
 
-=item L<Moose::Cookbook::Meta::Recipe6> - A method metaclass for marking methods public or private
+=item L<Moose::Cookbook::Meta::PrivateOrPublic_MethodMetaclass>
 
 This recipe shows a custom method metaclass that implements making a
 method private.
 
-=item L<Moose::Cookbook::Meta::Recipe7> - Using a blessed array reference as an object instance
+=item L<Moose::Cookbook::Meta::GlobRef_InstanceMetaclass>
 
 This recipe shows an example of how you create your own meta-instance
 class. The meta-instance determines the internal structure of object
 instances and provide access to attribute slots.
 
-=item Moose::Cookbook::Meta::Recipe8 - Hooking into immutabilization (TODO)
+In this particular instance, we use a blessed glob reference as the instance
+instead of a blessed hash reference.
+
+=item Hooking into immutabilization (TODO)
 
 Moose has a feature known as "immutabilization". By calling C<<
 __PACKAGE__->meta()->make_immutable() >> after defining your class
@@ -167,27 +170,20 @@ if you plan to write your own C<MooseX> module.
 
 =over 4
 
-=item L<Moose::Cookbook::Extending::Recipe1> - Moose extension overview
+=item L<Moose::Cookbook::Extending::ExtensionOverview>
 
 There are quite a few ways to extend Moose. This recipe provides an
 overview of each method, and provides recommendations for when each is
 appropriate.
 
-=item L<Moose::Cookbook::Extending::Recipe2> - Providing a base object class role
+=item L<Moose::Cookbook::Extending::Debugging_BaseClassRole>
 
 Many base object class extensions can be implemented as roles. This
 example shows how to provide a base object class debugging role that
 is applied to any class that uses a notional C<MooseX::Debugging>
 module.
 
-=item L<Moose::Cookbook::Extending::Recipe3> - Providing an alternate base object class
-
-You may find that you want to provide an alternate base object class
-along with a meta extension, or maybe you just want to add some
-functionality to all your classes without typing C<extends
-'MyApp::Base'> over and over.
-
-=item L<Moose::Cookbook::Extending::Recipe4> - Acting like Moose.pm and providing sugar Moose-style
+=item L<Moose::Cookbook::Extending::Mooseish_MooseSugar>
 
 This recipe shows how to provide a replacement for C<Moose.pm>. You
 may want to do this as part of the API for a C<MooseX> module,
@@ -206,6 +202,19 @@ object class.
 
 =back
 
+=head1 Legacy Recipes
+
+These cover topics that are no longer considered best practice. We've kept
+them in case in you encounter these usages in the wild.
+
+=over 4
+
+=item L<Moose::Cookbook::Meta::Labeled_AttributeMetaclass>
+
+=item L<Moose::Cookbook::Meta::Table_ClassMetaclass>
+
+=back
+
 =head1 SEE ALSO
 
 =over 4