Skip to content
Browse files

Merge pull request #8 from Csson/master

Documentation has moved within the Moose::Cookbook::Roles namespace
  • Loading branch information...
2 parents 8f0c43a + 2d2f225 commit 504336e1c6beaeee0ceba5d59f1438708b4d47d1 @sartak committed
Showing with 2 additions and 2 deletions.
  1. +2 −2 lib/MooseX/Role/Parameterized/Tutorial.pod
4 lib/MooseX/Role/Parameterized/Tutorial.pod
@@ -8,14 +8,14 @@ MooseX::Role::Parameterized::Tutorial - why and how
Roles are composable units of behavior. They are useful for factoring out
functionality common to many classes from any part of your class hierarchy. See
-L<Moose::Cookbook::Roles::Recipe1> for an introduction to L<Moose::Role>.
+L<Moose::Cookbook::Roles::Comparable_CodeReuse> for an introduction to L<Moose::Role>.
While combining roles affords you a great deal of flexibility, individual roles
have very little in the way of configurability. Core Moose provides C<-alias>
for renaming methods and C<-excludes> for ignoring methods. These options are
primarily for resolving role conflicts. Depending on how much of a purist you are,
these options are I<solely> for resolving role conflicts. See
-L<Moose::Cookbook::Roles::Recipe2> for more about C<-alias> and C<-excludes>.
+L<Moose::Cookbook::Roles::Restartable_AdvancedComposition> for more about C<-alias> and C<-excludes>.
Because roles serve many different masters, they usually provide only the least
common denominator of functionality. To empower roles further, more

0 comments on commit 504336e

Please sign in to comment.
Something went wrong with that request. Please try again.