use strict;
use warnings FATAL => 'all';
-our $VERSION = '1.000_900'; # 1.0.900
+our $VERSION = '1.001000'; # 1.1.0
$VERSION = eval $VERSION;
our %INFO;
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_single_role_to_package($to, $roles[0]) if @roles == 1;
+ 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);
} keys %conflicts;
die $fail;
}
- $me->apply_single_role_to_package($to, $_) for @roles;
+ 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;
}
# grab role symbol table
my $stash = do { no strict 'refs'; \%{"${role}::"}};
my $not_methods = $info->{not_methods};
- +{
+ $info->{methods} ||= +{
# grab all code entries that aren't in the not_methods list
map {
my $code = *{$stash->{$_}}{CODE};
provided methods clash, an exception is raised unless the class provides
a method since this conflict indicates a potential problem.
-=head1 METHODS
-
-=head2 apply_roles_to_package
-
- Role::Tiny->apply_roles_to_package(
- 'Some::Package', 'Some::Role', 'Some::Other::Role'
- );
-
-Composes role with package. See also L<Role::Tiny::With>.
-
-=head2 apply_roles_to_object
-
- Role::Tiny->apply_roles_to_object($foo, qw(Some::Role1 Some::Role2));
-
-Composes roles in order into object directly. Object is reblessed into the
-resulting class.
-
-=head2 create_class_with_roles
-
- Role::Tiny->create_class_with_roles('Some::Base', qw(Some::Role1 Some::Role2));
-
-Creates a new class based on base, with the roles composed into it in order.
-New class is returned.
-
-=head1 SUBROUTINES
-
-=head2 does_role
-
- if (Role::Tiny::does_role($foo, 'Some::Role')) {
- ...
- }
-
-Returns true if class has been composed with role.
-
-This subroutine is also installed as ->does on any class a Role::Tiny is
-composed into unless that class already has an ->does method, so
-
- if ($foo->does('Some::Role')) {
- ...
- }
-
-will work for classes but to test a role, one must use ::does_role directly
-
=head1 IMPORTED SUBROUTINES
=head2 requires
a dependency. If your L<Role::Tiny> role uses modifiers you must depend on
both L<Class::Method::Modifiers> and L<Role::Tiny>.
+=head1 SUBROUTINES
+
+=head2 does_role
+
+ if (Role::Tiny::does_role($foo, 'Some::Role')) {
+ ...
+ }
+
+Returns true if class has been composed with role.
+
+This subroutine is also installed as ->does on any class a Role::Tiny is
+composed into unless that class already has an ->does method, so
+
+ if ($foo->does('Some::Role')) {
+ ...
+ }
+
+will work for classes but to test a role, one must use ::does_role directly
+
+=head1 METHODS
+
+=head2 apply_roles_to_package
+
+ Role::Tiny->apply_roles_to_package(
+ 'Some::Package', 'Some::Role', 'Some::Other::Role'
+ );
+
+Composes role with package. See also L<Role::Tiny::With>.
+
+=head2 apply_roles_to_object
+
+ Role::Tiny->apply_roles_to_object($foo, qw(Some::Role1 Some::Role2));
+
+Composes roles in order into object directly. Object is reblessed into the
+resulting class.
+
+=head2 create_class_with_roles
+
+ Role::Tiny->create_class_with_roles('Some::Base', qw(Some::Role1 Some::Role2));
+
+Creates a new class based on base, with the roles composed into it in order.
+New class is returned.
+
=head1 SEE ALSO
L<Role::Tiny> is the attribute-less subset of L<Moo::Role>; L<Moo::Role> is
If you don't want method modifiers and do want to be forcibly restricted
to a single role application per class, Ovid's L<Role::Basic> exists. But
-Stevan Little (the L<Moose> author) don't find the additional restrictions
-to be amazingly helpful in most cases; L<Role::Basic>'s choices are more
-a guide to what you should prefer doing, to our mind, rather than something
-that needs to be enforced.
+Stevan Little (the L<Moose> author) and I don't find the additional
+restrictions to be amazingly helpful in most cases; L<Role::Basic>'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
perigrin - Chris Prather (cpan:PERIGRIN) <chris@prather.org>
+Mithaldu - Christian Walde (cpan:MITHALDU) <walde.christian@googlemail.com>
+
=head1 COPYRIGHT
Copyright (c) 2010-2012 the Role::Tiny L</AUTHOR> and L</CONTRIBUTORS>