From: Stevan Little Date: Sun, 5 Nov 2006 18:28:55 +0000 (+0000) Subject: 0.15 X-Git-Tag: 0_16~1 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=ecb59493ea0e2ccb95c40bd2131f3492362cd48b;p=gitmo%2FMoose.git 0.15 --- diff --git a/Build.PL b/Build.PL index d47c50e..e754d22 100644 --- a/Build.PL +++ b/Build.PL @@ -11,7 +11,7 @@ my $build = Module::Build->new( requires => { 'Scalar::Util' => $win32 ? '1.17' : '1.18', 'Carp' => '0', - 'Class::MOP' => '0.35', + 'Class::MOP' => '0.36', 'Sub::Name' => '0.02', 'Sub::Exporter' => '0.954', 'Sub::Install' => '0.92', diff --git a/Changes b/Changes index 3f1ffe0..d28bc9f 100644 --- a/Changes +++ b/Changes @@ -1,6 +1,6 @@ Revision history for Perl extension Moose -0.15 +0.15 Sun. Nov. 5, 2006 ++ NOTE ++ This version of Moose *must* have Class::MOP 0.36 in order to work correctly. A number of small internal tweaks have diff --git a/lib/Moose.pm b/lib/Moose.pm index 0f98b57..3264473 100644 --- a/lib/Moose.pm +++ b/lib/Moose.pm @@ -1,6 +1,4 @@ -use lib '/Users/stevan/Projects/Moose/Moose/Class-MOP/trunk/lib'; - package Moose; use strict; diff --git a/lib/Moose/Cookbook/FAQ.pod b/lib/Moose/Cookbook/FAQ.pod index 6b2b1fd..ba66ea7 100644 --- a/lib/Moose/Cookbook/FAQ.pod +++ b/lib/Moose/Cookbook/FAQ.pod @@ -24,12 +24,12 @@ Since development is still happening, regular upgrades are a fact of life. This can be hairy in production, so if this makes you quake with fear, you might want to wait a few months. -Then comes speed of execution. Moose is actually pretty fast, -and makes great effort to stay out of your way when you don't -want it there. However, certain parts of Moose are slow, such -as compile time setup, introspection and object construction -(only because it uses introspection). See L -below for a deeper discussion on the subject. +Then comes speed of execution. In some ways, Moose is actually +pretty fast and makes great effort to stay out of your way when +you don't want it there. However, certain parts of Moose are +slow, such as compile time setup, introspection and object +construction (only because it uses introspection). See +L below for a deeper discussion on the subject. =head3 Is Moose's API stable? diff --git a/lib/Moose/Meta/Method.pm b/lib/Moose/Meta/Method.pm index 4907a70..bd97cd1 100644 --- a/lib/Moose/Meta/Method.pm +++ b/lib/Moose/Meta/Method.pm @@ -15,15 +15,13 @@ __END__ =head1 NAME -=head1 SYNOPOSIS +Moose::Meta::Method - A Moose Method metaclass =head1 DESCRIPTION -=head1 METHODS - -=over 4 - -=back +For now, this is nothing but a subclass of Class::MOP::Method, +but with the expanding role of the method sub-protocol, it might +be more useful later on. =head1 BUGS diff --git a/lib/Moose/Meta/Method/Accessor.pm b/lib/Moose/Meta/Method/Accessor.pm index 0891d6b..0fa004c 100644 --- a/lib/Moose/Meta/Method/Accessor.pm +++ b/lib/Moose/Meta/Method/Accessor.pm @@ -1,6 +1,4 @@ -use lib '/Users/stevan/Projects/Moose/Moose/Class-MOP/trunk/lib'; - package Moose::Meta::Method::Accessor; use strict; @@ -208,24 +206,26 @@ __END__ =head1 NAME -=head1 SYNOPOSIS +Moose::Meta::Method::Accessor - A Moose Method metaclass for accessors =head1 DESCRIPTION +This is a subclass of L and it's primary +responsibility is to generate the accessor methods for attributes. It +can handle both closure based accessors, as well as inlined source based +accessors. + +This is a fairly new addition to the MOP, but this will play an important +role in the optimization strategy we are currently following. + =head1 METHODS =over 4 -=item B - =item B -=item B - =item B -=item B - =item B =back diff --git a/lib/Moose/Meta/Method/Overriden.pm b/lib/Moose/Meta/Method/Overriden.pm index 7d04326..7a9fd6a 100644 --- a/lib/Moose/Meta/Method/Overriden.pm +++ b/lib/Moose/Meta/Method/Overriden.pm @@ -15,15 +15,16 @@ __END__ =head1 NAME -=head1 SYNOPOSIS +Moose::Meta::Method::Overriden - A Moose Method metaclass for overriden methods =head1 DESCRIPTION -=head1 METHODS +This is primarily used to tag methods created with the C keyword. It +is currently just a subclass of L. -=over 4 - -=back +Later releases will likely encapsulate the C behavior of overriden methods, +rather than that being the responsibility of the class. But this is low priority +for now. =head1 BUGS diff --git a/lib/Moose/Meta/Role/Method.pm b/lib/Moose/Meta/Role/Method.pm index b95973d..041287e 100644 --- a/lib/Moose/Meta/Role/Method.pm +++ b/lib/Moose/Meta/Role/Method.pm @@ -16,15 +16,13 @@ __END__ =head1 NAME -=head1 SYNOPOSIS +Moose::Meta::Role::Method - A Moose Method metaclass for Roles =head1 DESCRIPTION -=head1 METHODS - -=over 4 - -=back +This is primarily used to mark methods coming from a role +as being different. Right now it is nothing but a subclass +of L. =head1 BUGS diff --git a/lib/Moose/Meta/TypeConstraint/Union.pm b/lib/Moose/Meta/TypeConstraint/Union.pm index 0e43472..036c426 100644 --- a/lib/Moose/Meta/TypeConstraint/Union.pm +++ b/lib/Moose/Meta/TypeConstraint/Union.pm @@ -117,43 +117,69 @@ __END__ =head1 NAME -=head1 SYNOPOSIS +Moose::Meta::TypeConstraint::Union - A union of Moose type constraints =head1 DESCRIPTION +This metaclass represents a union of Moose type constraints. More +details to be explained later (possibly in a Cookbook::Recipe). + +This actually used to be part of Moose::Meta::TypeConstraint, but it +is now better off in it's own file. + =head1 METHODS +This class is not a subclass of Moose::Meta::TypeConstraint, +but it does provide the same API + =over 4 -=item B +=item B -=item B +=item B -=item B +=item B + +=item B =item B -=item B +=back -=item B +=head2 Overriden methods + +=over 4 + +=item B + +=item B + +=item B =item B =item B -=item B +=back -=item B +=head2 Empty or Stub methods -=item B +These methods tend to not be very relevant in +the context of a union. Either that or they are +just difficult to specify and not very useful +anyway. They are here for completeness. -=item B +=over 4 =item B -=item B +=item B -=item B +=item B + +=item B + +=item B =back