Howdy, The attached patch fixes some minor issues I found in Moose::Manual.
-- Matt http://ftbfs.org/
diff --git a/lib/Moose/Manual/MOP.pod b/lib/Moose/Manual/MOP.pod index e1c9c4d..03f002b 100644 --- a/lib/Moose/Manual/MOP.pod +++ b/lib/Moose/Manual/MOP.pod @@ -128,10 +128,10 @@ class is immutable, calling any of these update methods will throw an exception. You can make a class mutable again simply by calling C<< -$metaclass->make_mutable >>. Once you're done changing it, you can -restore immutability by calling C<< $metaclass->make_immutable >>. +$meta->make_mutable >>. Once you're done changing it, you can +restore immutability by calling C<< $meta->make_immutable >>. -However, the most common use for this part of of the meta API is as +However, the most common use for this part of the meta API is as part of Moose extensions. These extensions should assume that they are being run before you make a class immutable. diff --git a/lib/Moose/Manual/MooseX.pod b/lib/Moose/Manual/MooseX.pod index 607bf35..7cac13f 100644 --- a/lib/Moose/Manual/MooseX.pod +++ b/lib/Moose/Manual/MooseX.pod @@ -80,7 +80,7 @@ arguments. package User; use Moose; - use MooseX::Params::Validate qw( validatep ); + use MooseX::Params::Validate; sub login { my $self = shift; @@ -166,7 +166,7 @@ cool, but still new and experimental. This extension helps you build a type library for your application. It also lets you predeclare type names and use them as barewords. - use MooseX::Types -declare => ['PosInt']; + use MooseX::Types -declare => ['PositiveInt']; use MooseX::Types::Moose 'Int'; subtype PositiveInt @@ -221,7 +221,7 @@ file, and signal handling. If you find yourself wanting a role that customizes itself for each consumer, this is the tool for you. With this module, you can create a -role that accepts parameters and generates attributes, methods, etc on +role that accepts parameters and generates attributes, methods, etc. on a customized basis for each consumer. =head2 L<MooseX::POE> diff --git a/lib/Moose/Manual/Types.pod b/lib/Moose/Manual/Types.pod index 7b623d1..ab67bfb 100644 --- a/lib/Moose/Manual/Types.pod +++ b/lib/Moose/Manual/Types.pod @@ -69,7 +69,7 @@ can even do something like C<HashRef[ArrayRef[Str]]>. The C<Maybe[`a]> type deserves a special mention. Used by itself, it doesn't really mean anything (and is equivalent to C<Item>). When it is parameterized, it means that the value is either C<undef> or the -parameterized type. So C<Maybe[Int]> means an integer or C<undef> +parameterized type. So C<Maybe[Int]> means an integer or C<undef>. For more details on the type hierarchy, see L<Moose::Util::TypeConstraints>. @@ -403,7 +403,7 @@ C<find_type_constraint> function exported by L<Moose::Util::TypeConstraints>: class_type('MyApp::User') - unless find_type_constraint('MyApp::User') || ; + unless find_type_constraint('MyApp::User'); This sort of "find or create" logic is simple to write, and will let you work around load order issues.