X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FRole%2FTiny.pm;h=04a44d15fbf98ec0ac1c1e5db7e979cb42be02b8;hb=123a5a6e906ff637e8527949e292efb60ea68724;hp=8ddc074a458e6e1f5c17196e948377914c6cd2f9;hpb=385f50873b724645e2fea1da9d53baea5f6d782c;p=gitmo%2FRole-Tiny.git diff --git a/lib/Role/Tiny.pm b/lib/Role/Tiny.pm index 8ddc074..04a44d1 100644 --- a/lib/Role/Tiny.pm +++ b/lib/Role/Tiny.pm @@ -6,12 +6,13 @@ sub _getstash { \%{"$_[0]::"} } use strict; use warnings FATAL => 'all'; -our $VERSION = '1.000000'; # 1.0.0 +our $VERSION = '1.001002'; # 1.1.2 $VERSION = eval $VERSION; our %INFO; our %APPLIED_TO; our %COMPOSED; +our %COMPOSITE_INFO; # Module state workaround totally stolen from Zefram's Module::Runtime. @@ -50,27 +51,28 @@ sub import { *{_getglob "${target}::${type}"} = sub { require Class::Method::Modifiers; push @{$INFO{$target}{modifiers}||=[]}, [ $type => @_ ]; + return; }; } *{_getglob "${target}::requires"} = sub { push @{$INFO{$target}{requires}||=[]}, @_; + return; }; *{_getglob "${target}::with"} = sub { - die "Only one role supported at a time by with" if @_ > 1; - $me->apply_role_to_package($target, $_[0]); + $me->apply_roles_to_package($target, @_); + return; }; # grab all *non-constant* (stash slot is not a scalarref) subs present # in the symbol table and store their refaddrs (no need to forcibly # inflate constant subs into real subs) - also add '' to here (this - # is used later) - @{$INFO{$target}{not_methods}={}}{ - '', map { *$_{CODE}||() } grep !ref($_), values %$stash - } = (); + # is used later) with a map to the coderefs in case of copying or re-use + my @not_methods = ('', map { *$_{CODE}||() } grep !ref($_), values %$stash); + @{$INFO{$target}{not_methods}={}}{@not_methods} = @not_methods; # a role does itself $APPLIED_TO{$target} = { $target => undef }; } -sub apply_role_to_package { +sub apply_single_role_to_package { my ($me, $to, $role) = @_; _load_module($role); @@ -106,6 +108,14 @@ sub create_class_with_roles { die "No roles supplied!" unless @roles; + { + my %seen; + $seen{$_}++ for @roles; + if (my @dupes = grep $seen{$_} > 1, @roles) { + die "Duplicated roles: ".join(', ', @dupes); + } + } + my $new_name = join( '__WITH__', $superclass, my $compose_name = join '__AND__', @roles ); @@ -123,6 +133,18 @@ sub create_class_with_roles { require MRO::Compat; } + my %conflicts = %{$me->_composite_info_for(@roles)->{conflicts}}; + if (keys %conflicts) { + my $fail = + join "\n", + map { + "Method name conflict for '$_' between roles " + ."'".join(' and ', sort values %{$conflicts{$_}})."'" + .", cannot apply these simultaneously to an object." + } keys %conflicts; + die $fail; + } + my @composable = map $me->_composable_package_for($_), reverse @roles; *{_getglob("${new_name}::ISA")} = [ @composable, $superclass ]; @@ -144,6 +166,47 @@ sub create_class_with_roles { return $new_name; } +# preserved for compat, and apply_roles_to_package calls it to allow an +# updated Role::Tiny to use a non-updated Moo::Role + +sub apply_role_to_package { shift->apply_single_role_to_package(@_) } + +sub apply_roles_to_package { + my ($me, $to, @roles) = @_; + + return $me->apply_role_to_package($to, $roles[0]) if @roles == 1; + + my %conflicts = %{$me->_composite_info_for(@roles)->{conflicts}}; + delete $conflicts{$_} for $me->_concrete_methods_of($to); + if (keys %conflicts) { + my $fail = + join "\n", + map { + "Due to a method name conflict between roles " + ."'".join(' and ', sort values %{$conflicts{$_}})."'" + .", the method '$_' must be implemented by '${to}'" + } keys %conflicts; + die $fail; + } + delete $INFO{$to}{methods}; # reset since we're about to add methods + $me->apply_role_to_package($to, $_) for @roles; + $APPLIED_TO{$to}{join('|',@roles)} = 1; +} + +sub _composite_info_for { + my ($me, @roles) = @_; + $COMPOSITE_INFO{join('|', sort @roles)} ||= do { + _load_module($_) for @roles; + my %methods; + foreach my $role (@roles) { + my $this_methods = $me->_concrete_methods_of($role); + $methods{$_}{$this_methods->{$_}} = $role for keys %$this_methods; + } + delete $methods{$_} for grep keys(%{$methods{$_}}) == 1, keys %methods; + +{ conflicts => \%methods } + }; +} + sub _composable_package_for { my ($me, $role) = @_; my $composed_name = 'Role::Tiny::_COMPOSABLE::'.$role; @@ -185,18 +248,18 @@ sub _check_requires { sub _concrete_methods_of { my ($me, $role) = @_; my $info = $INFO{$role}; - $info->{methods} ||= do { - # grab role symbol table - my $stash = do { no strict 'refs'; \%{"${role}::"}}; - my $not_methods = $info->{not_methods}; - +{ - # grab all code entries that aren't in the not_methods list - map { - my $code = *{$stash->{$_}}{CODE}; - # rely on the '' key we added in import for "no code here" - exists $not_methods->{$code||''} ? () : ($_ => $code) - } grep !ref($stash->{$_}), keys %$stash - }; + # grab role symbol table + my $stash = do { no strict 'refs'; \%{"${role}::"}}; + # reverse so our keys become the values (captured coderefs) in case + # they got copied or re-used since + my $not_methods = { reverse %{$info->{not_methods}||{}} }; + $info->{methods} ||= +{ + # grab all code entries that aren't in the not_methods list + map { + my $code = *{$stash->{$_}}{CODE}; + # rely on the '' key we added in import for "no code here" + exists $not_methods->{$code||''} ? () : ($_ => $code) + } grep !ref($stash->{$_}), keys %$stash }; } @@ -266,6 +329,8 @@ Role::Tiny - Roles. Like a nouvelle cuisine portion size slice of Moose. sub bar { ... } + around baz => sub { ... } + 1; else where @@ -279,8 +344,13 @@ else where sub foo { ... } + # baz is wrapped in the around modifier by Class::Method::Modifiers + sub baz { ... } + 1; +If you wanted attributes as well, look at L. + =head1 DESCRIPTION C is a minimalist role composition tool. @@ -305,31 +375,71 @@ role application will fail loudly. =back Unlike L, where the B class inherited from "wins," role -composition is the other way around, where first wins. In a more complete -system (see L) roles are checked to see if they clash. The goal of this -is to be much simpler, hence disallowing composition of multiple roles at once. +composition is the other way around, where the class wins. If multiple roles +are applied in a single call (single with statement), then if any of their +provided methods clash, an exception is raised unless the class provides +a method since this conflict indicates a potential problem. -=head1 METHODS +=head1 IMPORTED SUBROUTINES -=head2 apply_role_to_package +=head2 requires - Role::Tiny->apply_role_to_package('Some::Package', 'Some::Role'); + requires qw(foo bar); -Composes role with package. See also L. +Declares a list of methods that must be defined to compose role. -=head2 apply_roles_to_object +=head2 with - Role::Tiny->apply_roles_to_object($foo, qw(Some::Role1 Some::Role2)); + with 'Some::Role1'; -Composes roles in order into object directly. Object is reblessed into the -resulting class. + with 'Some::Role1', 'Some::Role2'; -=head2 create_class_with_roles +Composes another role into the current role (or class via L). - Role::Tiny->create_class_with_roles('Some::Base', qw(Some::Role1 Some::Role2)); +If you have conflicts and want to resolve them in favour of Some::Role1 you +can instead write: -Creates a new class based on base, with the roles composed into it in order. -New class is returned. + with 'Some::Role1'; + with 'Some::Role2'; + +If you have conflicts and want to resolve different conflicts in favour of +different roles, please refactor your codebase. + +=head2 before + + before foo => sub { ... }; + +See L<< Class::Method::Modifiers/before method(s) => sub { ... } >> for full +documentation. + +Note that since you are not required to use method modifiers, +L is lazily loaded and we do not declare it as +a dependency. If your L role uses modifiers you must depend on +both L and L. + +=head2 around + + around foo => sub { ... }; + +See L<< Class::Method::Modifiers/around method(s) => sub { ... } >> for full +documentation. + +Note that since you are not required to use method modifiers, +L is lazily loaded and we do not declare it as +a dependency. If your L role uses modifiers you must depend on +both L and L. + +=head2 after + + after foo => sub { ... }; + +See L<< Class::Method::Modifiers/after method(s) => sub { ... } >> for full +documentation. + +Note that since you are not required to use method modifiers, +L is lazily loaded and we do not declare it as +a dependency. If your L role uses modifiers you must depend on +both L and L. =head1 SUBROUTINES @@ -350,42 +460,41 @@ composed into unless that class already has an ->does method, so will work for classes but to test a role, one must use ::does_role directly -=head1 IMPORTED SUBROUTINES - -=head2 requires - - requires qw(foo bar); +=head1 METHODS -Declares a list of methods that must be defined to compose role. +=head2 apply_roles_to_package -=head2 with + Role::Tiny->apply_roles_to_package( + 'Some::Package', 'Some::Role', 'Some::Other::Role' + ); - with 'Some::Role1'; - with 'Some::Role2'; - -Composes another role into the current role. Only one role may be composed in -at a time to allow the code to remain as simple as possible. +Composes role with package. See also L. -=head2 before +=head2 apply_roles_to_object - before foo => sub { ... }; + Role::Tiny->apply_roles_to_object($foo, qw(Some::Role1 Some::Role2)); -See L<< Class::Method::Modifiers/before method(s) => sub { ... } >> for full -documentation. +Composes roles in order into object directly. Object is reblessed into the +resulting class. -=head2 around +=head2 create_class_with_roles - around foo => sub { ... }; + Role::Tiny->create_class_with_roles('Some::Base', qw(Some::Role1 Some::Role2)); -See L<< Class::Method::Modifiers/around method(s) => sub { ... } >> for full -documentation. +Creates a new class based on base, with the roles composed into it in order. +New class is returned. -=head2 after +=head1 SEE ALSO - after foo => sub { ... }; +L is the attribute-less subset of L; L is +a meta-protocol-less subset of the king of role systems, L. -See L<< Class::Method::Modifiers/after method(s) => sub { ... } >> for full -documentation. +If you don't want method modifiers and do want to be forcibly restricted +to a single role application per class, Ovid's L exists. But +Stevan Little (the L author) and I don't find the additional +restrictions to be amazingly helpful in most cases; L's choices +are more a guide to what you should prefer doing, to our mind, rather than +something that needs to be enforced. =head1 AUTHOR @@ -411,6 +520,8 @@ doy - Jesse Luehrs (cpan:DOY) perigrin - Chris Prather (cpan:PERIGRIN) +Mithaldu - Christian Walde (cpan:MITHALDU) + =head1 COPYRIGHT Copyright (c) 2010-2012 the Role::Tiny L and L