9 use Sub::Name 'subname';
13 our $VERSION = '0.04';
15 use Moose::Meta::Role;
16 use Moose::Util::TypeConstraints;
19 my ( $CALLER, %METAS );
24 return $METAS{$role} if exists $METAS{$role};
26 # make a subtype for each Moose class
29 => where { $_->does($role) }
30 unless find_type_constraint($role);
33 if ($role->can('meta')) {
34 $meta = $role->meta();
35 (blessed($meta) && $meta->isa('Moose::Meta::Role'))
36 || confess "Whoops, not møøsey enough";
39 $meta = Moose::Meta::Role->new(role_name => $role);
40 $meta->_role_meta->add_method('meta' => sub { $meta })
43 return $METAS{$role} = $meta;
49 my $meta = _find_meta();
50 return subname 'Moose::Role::extends' => sub {
51 confess "Moose::Role does not currently support 'extends'"
55 my $meta = _find_meta();
56 return subname 'Moose::Role::with' => sub ($;@) {
58 Moose::_load_all_classes(@roles);
59 ($_->can('meta') && $_->meta->isa('Moose::Meta::Role'))
60 || confess "You can only consume roles, $_ is not a Moose role"
62 if (scalar @roles == 1) {
63 $roles[0]->meta->apply($meta);
66 Moose::Meta::Role->combine(
67 map { $_->meta } @roles
73 my $meta = _find_meta();
74 return subname 'Moose::Role::requires' => sub ($;@) {
75 $meta->add_required_methods(@_);
79 my $meta = _find_meta();
80 return subname 'Moose::Role::excludes' => sub ($;@) {
81 $meta->add_excluded_roles(@_);
85 my $meta = _find_meta();
86 return subname 'Moose::Role::has' => sub ($;%) {
87 my ($name, %options) = @_;
88 $meta->add_attribute($name, %options)
92 my $meta = _find_meta();
93 return subname 'Moose::Role::before' => sub (@&) {
95 $meta->add_before_method_modifier($_, $code) for @_;
99 my $meta = _find_meta();
100 return subname 'Moose::Role::after' => sub (@&) {
102 $meta->add_after_method_modifier($_, $code) for @_;
106 my $meta = _find_meta();
107 return subname 'Moose::Role::around' => sub (@&) {
109 $meta->add_around_method_modifier($_, $code) for @_;
113 my $meta = _find_meta();
114 return subname 'Moose::Role::super' => sub {};
117 my $meta = _find_meta();
118 return subname 'Moose::Role::override' => sub ($&) {
119 my ($name, $code) = @_;
120 $meta->add_override_method_modifier($name, $code);
124 my $meta = _find_meta();
125 return subname 'Moose::Role::inner' => sub {
126 confess "Moose::Role does not currently support 'inner'";
130 my $meta = _find_meta();
131 return subname 'Moose::Role::augment' => sub {
132 confess "Moose::Role does not currently support 'augment'";
136 return \&Carp::confess;
139 return \&Scalar::Util::blessed;
143 my $exporter = Sub::Exporter::build_exporter({
144 exports => \%exports,
153 # we should never export to main
154 return if $CALLER eq 'main';
169 Moose::Role - The Moose Role
181 my ($self, $other) = @_;
182 !$self->equal($other);
185 # ... then in your classes
195 my ($self, $other) = @_;
196 $self->as_float == $other->as_float;
201 Role support in Moose is coming along quite well. It's best documentation
202 is still the the test suite, but it is fairly safe to assume Perl 6 style
203 behavior, and then either refer to the test suite, or ask questions on
204 #moose if something doesn't quite do what you expect. More complete
205 documentation is planned and will be included with the next official
206 (non-developer) release.
208 =head1 EXPORTED FUNCTIONS
210 Currently Moose::Role supports all of the functions that L<Moose> exports,
211 but differs slightly in how some items are handled (see L<CAVEATS> below
214 Moose::Role also offers two role specific keyword exports:
218 =item B<requires (@method_names)>
220 Roles can require that certain methods are implemented by any class which
223 =item B<excludes (@role_names)>
225 Roles can C<exclude> other roles, in effect saying "I can never be combined
226 with these C<@role_names>". This is a feature which should not be used
233 The role support now has only a few caveats. They are as follows:
239 Roles cannot use the C<extends> keyword, it will throw an exception for now.
240 The same is true of the C<augment> and C<inner> keywords (not sure those
241 really make sense for roles). All other Moose keywords will be I<deferred>
242 so that they can be applied to the consuming class.
246 Role composition does it's best to B<not> be order sensitive when it comes
247 to conflict resolution and requirements detection. However, it is order
248 sensitive when it comes to method modifiers. All before/around/after modifiers
249 are included whenever a role is composed into a class, and then are applied
250 in the order the roles are used. This too means that there is no conflict for
251 before/around/after modifiers as well.
253 In most cases, this will be a non issue, however it is something to keep in
254 mind when using method modifiers in a role. You should never assume any
259 The C<requires> keyword currently only works with actual methods. A method
260 modifier (before/around/after and override) will not count as a fufillment
261 of the requirement, and neither will an autogenerated accessor for an attribute.
263 It is likely that the attribute accessors will eventually be allowed to fufill
264 those requirements, either that or we will introduce a C<requires_attr> keyword
265 of some kind instead. This descision has not yet been finalized.
271 All complex software has bugs lurking in it, and this module is no
272 exception. If you find a bug please either email me, or add the bug
277 Stevan Little E<lt>stevan@iinteractive.comE<gt>
279 Christian Hansen E<lt>chansen@cpan.orgE<gt>
281 =head1 COPYRIGHT AND LICENSE
283 Copyright 2006 by Infinity Interactive, Inc.
285 L<http://www.iinteractive.com>
287 This library is free software; you can redistribute it and/or modify
288 it under the same terms as Perl itself.