Commit | Line | Data |
fcd84ca9 |
1 | package Moose; |
d1e17c7f |
2 | use strict; |
3 | use warnings; |
fcd84ca9 |
4 | |
ecb1297a |
5 | use 5.008; |
6 | |
21f1e231 |
7 | use Scalar::Util 'blessed'; |
e2095e4a |
8 | use Carp 'confess'; |
fcd84ca9 |
9 | |
1fa1a58d |
10 | use Moose::Deprecated; |
5bd4db9b |
11 | use Moose::Exporter; |
7f18097c |
12 | |
38bf2a25 |
13 | use Class::MOP; |
ef1d5f4b |
14 | |
c0e30cf5 |
15 | use Moose::Meta::Class; |
7415b2cb |
16 | use Moose::Meta::TypeConstraint; |
7c13858b |
17 | use Moose::Meta::TypeCoercion; |
78cd1d3b |
18 | use Moose::Meta::Attribute; |
ddd0ec20 |
19 | use Moose::Meta::Instance; |
c0e30cf5 |
20 | |
0779da92 |
21 | use Moose::Object; |
22 | |
d67145ed |
23 | use Moose::Meta::Role; |
0779da92 |
24 | use Moose::Meta::Role::Composite; |
25 | use Moose::Meta::Role::Application; |
26 | use Moose::Meta::Role::Application::RoleSummation; |
27 | use Moose::Meta::Role::Application::ToClass; |
28 | use Moose::Meta::Role::Application::ToRole; |
29 | use Moose::Meta::Role::Application::ToInstance; |
d67145ed |
30 | |
7415b2cb |
31 | use Moose::Util::TypeConstraints; |
d7d8a8c7 |
32 | use Moose::Util (); |
a15dff8d |
33 | |
17e5e226 |
34 | use Moose::Meta::Attribute::Native; |
fafc8b9b |
35 | |
c245d69b |
36 | sub throw_error { |
d03bd989 |
37 | # FIXME This |
c245d69b |
38 | shift; |
39 | goto \&confess |
40 | } |
4c0b3599 |
41 | |
5bd4db9b |
42 | sub extends { |
d5447d26 |
43 | my $meta = shift; |
3d544ed5 |
44 | |
e2095e4a |
45 | Moose->throw_error("Must derive at least one class") unless @_; |
9bcfbab1 |
46 | |
5bd4db9b |
47 | # this checks the metaclass to make sure |
48 | # it is correct, sometimes it can get out |
49 | # of sync when the classes are being built |
d5447d26 |
50 | $meta->superclasses(@_); |
5bd4db9b |
51 | } |
a3c7e2fe |
52 | |
5bd4db9b |
53 | sub with { |
d5447d26 |
54 | Moose::Util::apply_all_roles(shift, @_); |
5bd4db9b |
55 | } |
9bcfbab1 |
56 | |
5bd4db9b |
57 | sub has { |
d5447d26 |
58 | my $meta = shift; |
59 | my $name = shift; |
e2095e4a |
60 | |
61 | Moose->throw_error('Usage: has \'name\' => ( key => value, ... )') |
db532c7d |
62 | if @_ % 2 == 1; |
e2095e4a |
63 | |
833b56a7 |
64 | my %options = ( definition_context => Moose::Util::_caller_info(), @_ ); |
5bd4db9b |
65 | my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ]; |
d5447d26 |
66 | $meta->add_attribute( $_, %options ) for @$attrs; |
5bd4db9b |
67 | } |
9bcfbab1 |
68 | |
5bd4db9b |
69 | sub before { |
d5447d26 |
70 | Moose::Util::add_method_modifier(shift, 'before', \@_); |
5bd4db9b |
71 | } |
72 | |
73 | sub after { |
d5447d26 |
74 | Moose::Util::add_method_modifier(shift, 'after', \@_); |
5bd4db9b |
75 | } |
76 | |
77 | sub around { |
d5447d26 |
78 | Moose::Util::add_method_modifier(shift, 'around', \@_); |
5bd4db9b |
79 | } |
80 | |
991933fb |
81 | our $SUPER_PACKAGE; |
82 | our $SUPER_BODY; |
83 | our @SUPER_ARGS; |
84 | |
5bd4db9b |
85 | sub super { |
991933fb |
86 | # This check avoids a recursion loop - see |
87 | # t/100_bugs/020_super_recursion.t |
88 | return if defined $SUPER_PACKAGE && $SUPER_PACKAGE ne caller(); |
89 | return unless $SUPER_BODY; $SUPER_BODY->(@SUPER_ARGS); |
5bd4db9b |
90 | } |
9bcfbab1 |
91 | |
5bd4db9b |
92 | sub override { |
d5447d26 |
93 | my $meta = shift; |
5bd4db9b |
94 | my ( $name, $method ) = @_; |
d5447d26 |
95 | $meta->add_override_method_modifier( $name => $method ); |
5bd4db9b |
96 | } |
9bcfbab1 |
97 | |
5bd4db9b |
98 | sub inner { |
99 | my $pkg = caller(); |
100 | our ( %INNER_BODY, %INNER_ARGS ); |
101 | |
102 | if ( my $body = $INNER_BODY{$pkg} ) { |
103 | my @args = @{ $INNER_ARGS{$pkg} }; |
104 | local $INNER_ARGS{$pkg}; |
105 | local $INNER_BODY{$pkg}; |
106 | return $body->(@args); |
107 | } else { |
108 | return; |
ce265cc3 |
109 | } |
5bd4db9b |
110 | } |
9bcfbab1 |
111 | |
5bd4db9b |
112 | sub augment { |
d5447d26 |
113 | my $meta = shift; |
5bd4db9b |
114 | my ( $name, $method ) = @_; |
d5447d26 |
115 | $meta->add_augment_method_modifier( $name => $method ); |
ce265cc3 |
116 | } |
9bcfbab1 |
117 | |
aedcb7d9 |
118 | Moose::Exporter->setup_import_methods( |
d5447d26 |
119 | with_meta => [ |
348715c4 |
120 | qw( extends with has before after around override augment ) |
97a93056 |
121 | ], |
122 | as_is => [ |
123 | qw( super inner ), |
5bd4db9b |
124 | \&Carp::confess, |
125 | \&Scalar::Util::blessed, |
126 | ], |
127 | ); |
128 | |
cc841c0e |
129 | sub init_meta { |
085fba61 |
130 | # This used to be called as a function. This hack preserves |
131 | # backwards compatibility. |
132 | if ( $_[0] ne __PACKAGE__ ) { |
d69a348e |
133 | Moose::Deprecated::deprecated( |
134 | feature => 'Moose::init_meta', |
135 | message => 'Calling Moose::init_meta as a function is deprecated', |
136 | ); |
137 | |
085fba61 |
138 | return __PACKAGE__->init_meta( |
139 | for_class => $_[0], |
140 | base_class => $_[1], |
141 | metaclass => $_[2], |
142 | ); |
143 | } |
7c4676ef |
144 | |
0338a411 |
145 | shift; |
146 | my %args = @_; |
147 | |
148 | my $class = $args{for_class} |
c245d69b |
149 | or Moose->throw_error("Cannot call init_meta without specifying a for_class"); |
085fba61 |
150 | my $base_class = $args{base_class} || 'Moose::Object'; |
151 | my $metaclass = $args{metaclass} || 'Moose::Meta::Class'; |
2937ed18 |
152 | my $meta_name = exists $args{meta_name} ? $args{meta_name} : 'meta'; |
cc841c0e |
153 | |
c245d69b |
154 | Moose->throw_error("The Metaclass $metaclass must be a subclass of Moose::Meta::Class.") |
cc841c0e |
155 | unless $metaclass->isa('Moose::Meta::Class'); |
156 | |
157 | # make a subtype for each Moose class |
158 | class_type($class) |
159 | unless find_type_constraint($class); |
160 | |
161 | my $meta; |
50d5df60 |
162 | |
163 | if ( $meta = Class::MOP::get_metaclass_by_name($class) ) { |
164 | unless ( $meta->isa("Moose::Meta::Class") ) { |
677eafe2 |
165 | my $error_message = "$class already has a metaclass, but it does not inherit $metaclass ($meta)."; |
166 | if ( $meta->isa('Moose::Meta::Role') ) { |
167 | Moose->throw_error($error_message . ' You cannot make the same thing a role and a class. Remove either Moose or Moose::Role.'); |
168 | } else { |
169 | Moose->throw_error($error_message); |
170 | } |
50d5df60 |
171 | } |
172 | } else { |
ed544690 |
173 | # no metaclass |
50d5df60 |
174 | |
175 | # now we check whether our ancestors have metaclass, and if so borrow that |
72825dcd |
176 | my ( undef, @isa ) = @{ mro::get_linear_isa($class) }; |
50d5df60 |
177 | |
178 | foreach my $ancestor ( @isa ) { |
179 | my $ancestor_meta = Class::MOP::get_metaclass_by_name($ancestor) || next; |
180 | |
ed086157 |
181 | my $ancestor_meta_class = $ancestor_meta->_real_ref_name; |
50d5df60 |
182 | |
183 | # if we have an ancestor metaclass that inherits $metaclass, we use |
41419b9e |
184 | # that. This is like _fix_metaclass_incompatibility, but we can do it now. |
50d5df60 |
185 | |
186 | # the case of having an ancestry is not very common, but arises in |
187 | # e.g. Reaction |
188 | unless ( $metaclass->isa( $ancestor_meta_class ) ) { |
189 | if ( $ancestor_meta_class->isa($metaclass) ) { |
190 | $metaclass = $ancestor_meta_class; |
191 | } |
192 | } |
193 | } |
194 | |
195 | $meta = $metaclass->initialize($class); |
196 | } |
197 | |
2937ed18 |
198 | if (defined $meta_name) { |
50d5df60 |
199 | # also check for inherited non moose 'meta' method? |
2937ed18 |
200 | my $existing = $meta->get_method($meta_name); |
d65bfd76 |
201 | if ($existing && !$existing->isa('Class::MOP::Method::Meta')) { |
df100ac2 |
202 | Carp::cluck "Moose is overwriting an existing method named " |
2937ed18 |
203 | . "$meta_name in class $class with a method " |
204 | . "which returns the class's metaclass. If this is " |
205 | . "actually what you want, you should remove the " |
206 | . "existing method, otherwise, you should rename or " |
207 | . "disable this generated method using the " |
208 | . "'-meta_name' option to 'use Moose'."; |
d65bfd76 |
209 | } |
2937ed18 |
210 | $meta->_add_meta_method($meta_name); |
cc841c0e |
211 | } |
212 | |
213 | # make sure they inherit from Moose::Object |
214 | $meta->superclasses($base_class) |
215 | unless $meta->superclasses(); |
216 | |
217 | return $meta; |
218 | } |
219 | |
085fba61 |
220 | # This may be used in some older MooseX extensions. |
221 | sub _get_caller { |
222 | goto &Moose::Exporter::_get_caller; |
223 | } |
224 | |
8ecb1fa0 |
225 | ## make 'em all immutable |
226 | |
3cae4250 |
227 | $_->make_immutable( |
0779da92 |
228 | inline_constructor => 1, |
229 | constructor_name => "_new", |
3cae4250 |
230 | # these are Class::MOP accessors, so they need inlining |
231 | inline_accessors => 1 |
232 | ) for grep { $_->is_mutable } |
233 | map { $_->meta } |
234 | qw( |
0779da92 |
235 | Moose::Meta::Attribute |
236 | Moose::Meta::Class |
237 | Moose::Meta::Instance |
238 | |
0779da92 |
239 | Moose::Meta::TypeCoercion |
240 | Moose::Meta::TypeCoercion::Union |
241 | |
242 | Moose::Meta::Method |
243 | Moose::Meta::Method::Accessor |
244 | Moose::Meta::Method::Constructor |
245 | Moose::Meta::Method::Destructor |
74862722 |
246 | Moose::Meta::Method::Overridden |
0779da92 |
247 | Moose::Meta::Method::Augmented |
248 | |
249 | Moose::Meta::Role |
f785aad8 |
250 | Moose::Meta::Role::Attribute |
0779da92 |
251 | Moose::Meta::Role::Method |
252 | Moose::Meta::Role::Method::Required |
bb153262 |
253 | Moose::Meta::Role::Method::Conflicting |
0779da92 |
254 | |
255 | Moose::Meta::Role::Composite |
256 | |
257 | Moose::Meta::Role::Application |
258 | Moose::Meta::Role::Application::RoleSummation |
259 | Moose::Meta::Role::Application::ToClass |
260 | Moose::Meta::Role::Application::ToRole |
261 | Moose::Meta::Role::Application::ToInstance |
3cae4250 |
262 | ); |
8ecb1fa0 |
263 | |
f785aad8 |
264 | Moose::Meta::Mixin::AttributeCore->meta->make_immutable( |
265 | inline_constructor => 0, |
266 | constructor_name => undef, |
267 | ); |
268 | |
fcd84ca9 |
269 | 1; |
270 | |
ad46f524 |
271 | # ABSTRACT: A postmodern object system for Perl 5 |
272 | |
fcd84ca9 |
273 | __END__ |
274 | |
275 | =pod |
276 | |
fcd84ca9 |
277 | =head1 SYNOPSIS |
e522431d |
278 | |
279 | package Point; |
1cd45431 |
280 | use Moose; # automatically turns on strict and warnings |
26fbace8 |
281 | |
43d599e5 |
282 | has 'x' => (is => 'rw', isa => 'Int'); |
283 | has 'y' => (is => 'rw', isa => 'Int'); |
26fbace8 |
284 | |
e522431d |
285 | sub clear { |
286 | my $self = shift; |
287 | $self->x(0); |
26fbace8 |
288 | $self->y(0); |
e522431d |
289 | } |
26fbace8 |
290 | |
e522431d |
291 | package Point3D; |
292 | use Moose; |
26fbace8 |
293 | |
e522431d |
294 | extends 'Point'; |
26fbace8 |
295 | |
43d599e5 |
296 | has 'z' => (is => 'rw', isa => 'Int'); |
26fbace8 |
297 | |
e522431d |
298 | after 'clear' => sub { |
299 | my $self = shift; |
43d599e5 |
300 | $self->z(0); |
26fbace8 |
301 | }; |
2c0cbef7 |
302 | |
fcd84ca9 |
303 | =head1 DESCRIPTION |
304 | |
26fbace8 |
305 | Moose is an extension of the Perl 5 object system. |
e522431d |
306 | |
9b9da6f1 |
307 | The main goal of Moose is to make Perl 5 Object Oriented programming |
edd0727e |
308 | easier, more consistent, and less tedious. With Moose you can think |
6f894f30 |
309 | more about what you want to do and less about the mechanics of OOP. |
fcd84ca9 |
310 | |
6f894f30 |
311 | Additionally, Moose is built on top of L<Class::MOP>, which is a |
312 | metaclass system for Perl 5. This means that Moose not only makes |
313 | building normal Perl 5 objects better, but it provides the power of |
314 | metaclass programming as well. |
8bdc7f13 |
315 | |
f5909dca |
316 | =head2 New to Moose? |
317 | |
60eccd1e |
318 | If you're new to Moose, the best place to start is the |
319 | L<Moose::Manual> docs, followed by the L<Moose::Cookbook>. The intro |
320 | will show you what Moose is, and how it makes Perl 5 OO better. |
6f894f30 |
321 | |
322 | The cookbook recipes on Moose basics will get you up to speed with |
323 | many of Moose's features quickly. Once you have an idea of what Moose |
324 | can do, you can use the API documentation to get more detail on |
325 | features which interest you. |
f5909dca |
326 | |
28669f89 |
327 | =head2 Moose Extensions |
328 | |
12aed9a0 |
329 | The C<MooseX::> namespace is the official place to find Moose extensions. |
330 | These extensions can be found on the CPAN. The easiest way to find them |
331 | is to search for them (L<http://search.cpan.org/search?query=MooseX::>), |
332 | or to examine L<Task::Moose> which aims to keep an up-to-date, easily |
333 | installable list of Moose extensions. |
28669f89 |
334 | |
ceb61b4f |
335 | =head1 TRANSLATIONS |
336 | |
337 | Much of the Moose documentation has been translated into other languages. |
338 | |
339 | =over 4 |
340 | |
52a0d29a |
341 | =item Japanese |
342 | |
45902e41 |
343 | Japanese docs can be found at |
344 | L<http://perldoc.perlassociation.org/pod/Moose-Doc-JA/index.html>. The |
345 | source POD files can be found in GitHub: |
346 | L<http://github.com/jpa/Moose-Doc-JA> |
ceb61b4f |
347 | |
348 | =back |
349 | |
6ba6d68c |
350 | =head1 BUILDING CLASSES WITH MOOSE |
351 | |
68efb014 |
352 | Moose makes every attempt to provide as much convenience as possible during |
353 | class construction/definition, but still stay out of your way if you want it |
354 | to. Here are a few items to note when building classes with Moose. |
6ba6d68c |
355 | |
a6ae85e9 |
356 | When you C<use Moose>, Moose will set the class's parent class to |
357 | L<Moose::Object>, I<unless> the class using Moose already has a parent |
358 | class. In addition, specifying a parent with C<extends> will change the parent |
359 | class. |
6ba6d68c |
360 | |
1cd45431 |
361 | Moose will also manage all attributes (including inherited ones) that are |
362 | defined with C<has>. And (assuming you call C<new>, which is inherited from |
363 | L<Moose::Object>) this includes properly initializing all instance slots, |
364 | setting defaults where appropriate, and performing any type constraint checking |
365 | or coercion. |
6ba6d68c |
366 | |
004222dc |
367 | =head1 PROVIDED METHODS |
6ba6d68c |
368 | |
d03bd989 |
369 | Moose provides a number of methods to all your classes, mostly through the |
004222dc |
370 | inheritance of L<Moose::Object>. There is however, one exception. |
6ba6d68c |
371 | |
372 | =over 4 |
373 | |
374 | =item B<meta> |
375 | |
376 | This is a method which provides access to the current class's metaclass. |
377 | |
004222dc |
378 | =back |
379 | |
380 | =head1 EXPORTED FUNCTIONS |
381 | |
382 | Moose will export a number of functions into the class's namespace which |
383 | may then be used to set up the class. These functions all work directly |
384 | on the current class. |
385 | |
386 | =over 4 |
387 | |
6ba6d68c |
388 | =item B<extends (@superclasses)> |
389 | |
390 | This function will set the superclass(es) for the current class. |
391 | |
26fbace8 |
392 | This approach is recommended instead of C<use base>, because C<use base> |
393 | actually C<push>es onto the class's C<@ISA>, whereas C<extends> will |
394 | replace it. This is important to ensure that classes which do not have |
68efb014 |
395 | superclasses still properly inherit from L<Moose::Object>. |
6ba6d68c |
396 | |
2e7f6cf4 |
397 | Each superclass can be followed by a hash reference with options. Currently, |
398 | only L<-version|Class::MOP/Class Loading Options> is recognized: |
399 | |
400 | extends 'My::Parent' => { -version => 0.01 }, |
401 | 'My::OtherParent' => { -version => 0.03 }; |
402 | |
403 | An exception will be thrown if the version requirements are not |
404 | satisfied. |
405 | |
43d599e5 |
406 | =item B<with (@roles)> |
e9ec68d6 |
407 | |
d03bd989 |
408 | This will apply a given set of C<@roles> to the local class. |
e9ec68d6 |
409 | |
2e7f6cf4 |
410 | Like with C<extends>, each specified role can be followed by a hash |
411 | reference with a L<-version|Class::MOP/Class Loading Options> option: |
412 | |
413 | with 'My::Role' => { -version => 0.32 }, |
414 | 'My::Otherrole' => { -version => 0.23 }; |
415 | |
416 | The specified version requirements must be satisfied, otherwise an |
417 | exception will be thrown. |
418 | |
419 | If your role takes options or arguments, they can be passed along in the |
420 | hash reference as well. |
421 | |
b4291ab4 |
422 | =item B<has $name|@$names =E<gt> %options> |
6ba6d68c |
423 | |
b4291ab4 |
424 | This will install an attribute of a given C<$name> into the current class. If |
425 | the first parameter is an array reference, it will create an attribute for |
426 | every C<$name> in the list. The C<%options> are the same as those provided by |
427 | L<Class::MOP::Attribute>, in addition to the list below which are provided by |
428 | Moose (L<Moose::Meta::Attribute> to be more specific): |
6ba6d68c |
429 | |
430 | =over 4 |
431 | |
076c81ed |
432 | =item I<is =E<gt> 'rw'|'ro'> |
6ba6d68c |
433 | |
26fbace8 |
434 | The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read |
435 | only). These will create either a read/write accessor or a read-only |
6ba6d68c |
436 | accessor respectively, using the same name as the C<$name> of the attribute. |
437 | |
1b46b845 |
438 | If you need more control over how your accessors are named, you can |
439 | use the L<reader|Class::MOP::Attribute/reader>, |
440 | L<writer|Class::MOP::Attribute/writer> and |
441 | L<accessor|Class::MOP::Attribute/accessor> options inherited from |
442 | L<Class::MOP::Attribute>, however if you use those, you won't need the |
443 | I<is> option. |
6ba6d68c |
444 | |
076c81ed |
445 | =item I<isa =E<gt> $type_name> |
6ba6d68c |
446 | |
26fbace8 |
447 | The I<isa> option uses Moose's type constraint facilities to set up runtime |
448 | type checking for this attribute. Moose will perform the checks during class |
449 | construction, and within any accessors. The C<$type_name> argument must be a |
450 | string. The string may be either a class name or a type defined using |
9cca2e9e |
451 | Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints> |
c2a69ef1 |
452 | for information on how to define a new type, and how to retrieve type meta-data). |
6ba6d68c |
453 | |
daea75c9 |
454 | =item I<coerce =E<gt> (1|0)> |
455 | |
26fbace8 |
456 | This will attempt to use coercion with the supplied type constraint to change |
2e953f12 |
457 | the value passed into any accessors or constructors. You B<must> supply a type |
ebd95638 |
458 | constraint, and that type constraint B<must> define a coercion. See |
2e953f12 |
459 | L<Moose::Cookbook::Basics::Recipe5> for an example. |
daea75c9 |
460 | |
461 | =item I<does =E<gt> $role_name> |
462 | |
26fbace8 |
463 | This will accept the name of a role which the value stored in this attribute |
daea75c9 |
464 | is expected to have consumed. |
465 | |
466 | =item I<required =E<gt> (1|0)> |
467 | |
81bec8f8 |
468 | This marks the attribute as being required. This means a value must be |
be1355c0 |
469 | supplied during class construction, I<or> the attribute must be lazy |
470 | and have either a default or a builder. Note that c<required> does not |
471 | say anything about the attribute's value, which can be C<undef>. |
daea75c9 |
472 | |
473 | =item I<weak_ref =E<gt> (1|0)> |
474 | |
68efb014 |
475 | This will tell the class to store the value of this attribute as a weakened |
476 | reference. If an attribute is a weakened reference, it B<cannot> also be |
477 | coerced. |
daea75c9 |
478 | |
479 | =item I<lazy =E<gt> (1|0)> |
480 | |
26fbace8 |
481 | This will tell the class to not create this slot until absolutely necessary. |
daea75c9 |
482 | If an attribute is marked as lazy it B<must> have a default supplied. |
483 | |
9e93dd19 |
484 | =item I<auto_deref =E<gt> (1|0)> |
485 | |
1668f3d7 |
486 | This tells the accessor to automatically dereference the value of this |
487 | attribute when called in list context. The accessor will still return a |
606cc2a6 |
488 | reference when called in scalar context. If this behavior isn't desirable, |
489 | L<Moose::Meta::Attribute::Native::Trait::Array/elements> or |
490 | L<Moose::Meta::Attribute::Native::Trait::Hash/elements> may be a better |
491 | choice. The I<auto_deref> option is only legal if your I<isa> option is |
492 | either C<ArrayRef> or C<HashRef>. |
9e93dd19 |
493 | |
65e14c86 |
494 | =item I<trigger =E<gt> $code> |
495 | |
525129a5 |
496 | The I<trigger> option is a CODE reference which will be called after |
c25ca3a6 |
497 | the value of the attribute is set. The CODE ref is passed the |
edd0727e |
498 | instance itself, the updated value, and the original value if the |
c25ca3a6 |
499 | attribute was already set. |
3dda07f5 |
500 | |
501 | You B<can> have a trigger on a read-only attribute. |
010997ca |
502 | |
503 | B<NOTE:> Triggers will only fire when you B<assign> to the attribute, |
504 | either in the constructor, or using the writer. Default and built values will |
505 | B<not> cause the trigger to be fired. |
daea75c9 |
506 | |
c7761602 |
507 | =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | ROLETYPE | DUCKTYPE | CODE> |
2c0cbef7 |
508 | |
26fbace8 |
509 | The I<handles> option provides Moose classes with automated delegation features. |
510 | This is a pretty complex and powerful option. It accepts many different option |
511 | formats, each with its own benefits and drawbacks. |
38e3283b |
512 | |
1cd45431 |
513 | B<NOTE:> The class being delegated to does not need to be a Moose based class, |
514 | which is why this feature is especially useful when wrapping non-Moose classes. |
38e3283b |
515 | |
1cd45431 |
516 | All I<handles> option formats share the following traits: |
38e3283b |
517 | |
1cd45431 |
518 | You cannot override a locally defined method with a delegated method; an |
519 | exception will be thrown if you try. That is to say, if you define C<foo> in |
520 | your class, you cannot override it with a delegated C<foo>. This is almost never |
521 | something you would want to do, and if it is, you should do it by hand and not |
522 | use Moose. |
38e3283b |
523 | |
1cd45431 |
524 | You cannot override any of the methods found in Moose::Object, or the C<BUILD> |
525 | and C<DEMOLISH> methods. These will not throw an exception, but will silently |
526 | move on to the next method in the list. My reasoning for this is that you would |
527 | almost never want to do this, since it usually breaks your class. As with |
528 | overriding locally defined methods, if you do want to do this, you should do it |
529 | manually, not with Moose. |
38e3283b |
530 | |
d03bd989 |
531 | You do not I<need> to have a reader (or accessor) for the attribute in order |
532 | to delegate to it. Moose will create a means of accessing the value for you, |
533 | however this will be several times B<less> efficient then if you had given |
f3c4e20e |
534 | the attribute a reader (or accessor) to use. |
535 | |
38e3283b |
536 | Below is the documentation for each option format: |
537 | |
538 | =over 4 |
539 | |
540 | =item C<ARRAY> |
541 | |
26fbace8 |
542 | This is the most common usage for I<handles>. You basically pass a list of |
543 | method names to be delegated, and Moose will install a delegation method |
1cd45431 |
544 | for each one. |
38e3283b |
545 | |
546 | =item C<HASH> |
547 | |
26fbace8 |
548 | This is the second most common usage for I<handles>. Instead of a list of |
549 | method names, you pass a HASH ref where each key is the method name you |
550 | want installed locally, and its value is the name of the original method |
551 | in the class being delegated to. |
fd595040 |
552 | |
26fbace8 |
553 | This can be very useful for recursive classes like trees. Here is a |
5cfe3805 |
554 | quick example (soon to be expanded into a Moose::Cookbook recipe): |
38e3283b |
555 | |
1cd45431 |
556 | package Tree; |
38e3283b |
557 | use Moose; |
26fbace8 |
558 | |
38e3283b |
559 | has 'node' => (is => 'rw', isa => 'Any'); |
26fbace8 |
560 | |
38e3283b |
561 | has 'children' => ( |
562 | is => 'ro', |
563 | isa => 'ArrayRef', |
564 | default => sub { [] } |
565 | ); |
26fbace8 |
566 | |
38e3283b |
567 | has 'parent' => ( |
568 | is => 'rw', |
569 | isa => 'Tree', |
edd0727e |
570 | weak_ref => 1, |
38e3283b |
571 | handles => { |
572 | parent_node => 'node', |
26fbace8 |
573 | siblings => 'children', |
38e3283b |
574 | } |
575 | ); |
576 | |
1cd45431 |
577 | In this example, the Tree package gets C<parent_node> and C<siblings> methods, |
578 | which delegate to the C<node> and C<children> methods (respectively) of the Tree |
26fbace8 |
579 | instance stored in the C<parent> slot. |
38e3283b |
580 | |
9218b114 |
581 | You may also use an array reference to curry arguments to the original method. |
582 | |
583 | has 'thing' => ( |
584 | ... |
3c573ca4 |
585 | handles => { set_foo => [ set => 'foo' ] }, |
9218b114 |
586 | ); |
587 | |
588 | # $self->set_foo(...) calls $self->thing->set('foo', ...) |
589 | |
590 | The first element of the array reference is the original method name, and the |
3c573ca4 |
591 | rest is a list of curried arguments. |
9218b114 |
592 | |
38e3283b |
593 | =item C<REGEXP> |
594 | |
26fbace8 |
595 | The regexp option works very similar to the ARRAY option, except that it builds |
596 | the list of methods for you. It starts by collecting all possible methods of the |
597 | class being delegated to, then filters that list using the regexp supplied here. |
38e3283b |
598 | |
26fbace8 |
599 | B<NOTE:> An I<isa> option is required when using the regexp option format. This |
600 | is so that we can determine (at compile time) the method list from the class. |
38e3283b |
601 | Without an I<isa> this is just not possible. |
602 | |
c7761602 |
603 | =item C<ROLE> or C<ROLETYPE> |
c84f324f |
604 | |
c7761602 |
605 | With the role option, you specify the name of a role or a |
606 | L<role type|Moose::Meta::TypeConstraint::Role> whose "interface" then becomes |
607 | the list of methods to handle. The "interface" can be defined as; the methods |
608 | of the role and any required methods of the role. It should be noted that this |
609 | does B<not> include any method modifiers or generated attribute methods (which |
610 | is consistent with role composition). |
c84f324f |
611 | |
e3de240e |
612 | =item C<DUCKTYPE> |
613 | |
a6d8545f |
614 | With the duck type option, you pass a duck type object whose "interface" then |
edd0727e |
615 | becomes the list of methods to handle. The "interface" can be defined as the |
a6d8545f |
616 | list of methods passed to C<duck_type> to create a duck type object. For more |
617 | information on C<duck_type> please check |
e9c2746e |
618 | L<Moose::Util::TypeConstraints>. |
e3de240e |
619 | |
38e3283b |
620 | =item C<CODE> |
621 | |
1cd45431 |
622 | This is the option to use when you really want to do something funky. You should |
623 | only use it if you really know what you are doing, as it involves manual |
624 | metaclass twiddling. |
38e3283b |
625 | |
1cd45431 |
626 | This takes a code reference, which should expect two arguments. The first is the |
627 | attribute meta-object this I<handles> is attached to. The second is the |
628 | metaclass of the class being delegated to. It expects you to return a hash (not |
26fbace8 |
629 | a HASH ref) of the methods you want mapped. |
38e3283b |
630 | |
631 | =back |
2c0cbef7 |
632 | |
004222dc |
633 | =item I<metaclass =E<gt> $metaclass_name> |
634 | |
635 | This tells the class to use a custom attribute metaclass for this particular |
636 | attribute. Custom attribute metaclasses are useful for extending the |
637 | capabilities of the I<has> keyword: they are the simplest way to extend the MOP, |
edd0727e |
638 | but they are still a fairly advanced topic and too much to cover here. See |
5cfe3805 |
639 | L<Moose::Cookbook::Meta::Recipe1> for more information. |
004222dc |
640 | |
8a8856de |
641 | See L<Metaclass and Trait Name Resolution> for details on how a metaclass name |
642 | is resolved to a class name. |
004222dc |
643 | |
644 | =item I<traits =E<gt> [ @role_names ]> |
645 | |
d03bd989 |
646 | This tells Moose to take the list of C<@role_names> and apply them to the |
647 | attribute meta-object. This is very similar to the I<metaclass> option, but |
54f2996d |
648 | allows you to use more than one extension at a time. |
004222dc |
649 | |
8a8856de |
650 | See L<Metaclass and Trait Name Resolution> for details on how a trait name is |
651 | resolved to a role name. |
54f2996d |
652 | |
653 | Also see L<Moose::Cookbook::Meta::Recipe3> for a metaclass trait |
654 | example. |
004222dc |
655 | |
019f031d |
656 | =item I<builder> => Str |
010997ca |
657 | |
1b46b845 |
658 | The value of this key is the name of the method that will be called to |
659 | obtain the value used to initialize the attribute. See the L<builder |
660 | option docs in Class::MOP::Attribute|Class::MOP::Attribute/builder> |
edd0727e |
661 | and/or L<Moose::Cookbook::Basics::Recipe8> for more information. |
010997ca |
662 | |
019f031d |
663 | =item I<default> => SCALAR | CODE |
010997ca |
664 | |
665 | The value of this key is the default value which will initialize the attribute. |
666 | |
1b46b845 |
667 | NOTE: If the value is a simple scalar (string or number), then it can |
668 | be just passed as is. However, if you wish to initialize it with a |
669 | HASH or ARRAY ref, then you need to wrap that inside a CODE reference. |
670 | See the L<default option docs in |
671 | Class::MOP::Attribute|Class::MOP::Attribute/default> for more |
672 | information. |
010997ca |
673 | |
019f031d |
674 | =item I<clearer> => Str |
010997ca |
675 | |
edd0727e |
676 | Creates a method allowing you to clear the value. See the L<clearer option |
afd72e0c |
677 | docs in Class::MOP::Attribute|Class::MOP::Attribute/clearer> for more |
1b46b845 |
678 | information. |
010997ca |
679 | |
019f031d |
680 | =item I<predicate> => Str |
010997ca |
681 | |
afd72e0c |
682 | Creates a method to perform a basic test to see if a value has been set in the |
edd0727e |
683 | attribute. See the L<predicate option docs in |
afd72e0c |
684 | Class::MOP::Attribute|Class::MOP::Attribute/predicate> for more information. |
010997ca |
685 | |
019f031d |
686 | =item I<lazy_build> => (0|1) |
687 | |
688 | Automatically define lazy => 1 as well as builder => "_build_$attr", clearer => |
689 | "clear_$attr', predicate => 'has_$attr' unless they are already defined. |
690 | |
8c63a5c8 |
691 | =item I<initializer> => Str |
692 | |
693 | This may be a method name (referring to a method on the class with |
694 | this attribute) or a CODE ref. The initializer is used to set the |
695 | attribute value on an instance when the attribute is set during |
696 | instance initialization (but not when the value is being assigned |
697 | to). See the L<initializer option docs in |
698 | Class::MOP::Attribute|Class::MOP::Attribute/initializer> for more |
699 | information. |
019f031d |
700 | |
60dcf673 |
701 | =item I<documentation> => $string |
702 | |
703 | An arbitrary string that can be retrieved later by calling C<< |
704 | $attr->documentation >>. |
705 | |
706 | |
707 | |
6ba6d68c |
708 | =back |
709 | |
cd7eeaf5 |
710 | =item B<has +$name =E<gt> %options> |
711 | |
c7874946 |
712 | This is variation on the normal attribute creator C<has> which allows you to |
d03bd989 |
713 | clone and extend an attribute from a superclass or from a role. Here is an |
8d62bf6d |
714 | example of the superclass usage: |
cd7eeaf5 |
715 | |
716 | package Foo; |
717 | use Moose; |
26fbace8 |
718 | |
cd7eeaf5 |
719 | has 'message' => ( |
26fbace8 |
720 | is => 'rw', |
cd7eeaf5 |
721 | isa => 'Str', |
722 | default => 'Hello, I am a Foo' |
723 | ); |
26fbace8 |
724 | |
cd7eeaf5 |
725 | package My::Foo; |
726 | use Moose; |
26fbace8 |
727 | |
cd7eeaf5 |
728 | extends 'Foo'; |
26fbace8 |
729 | |
cd7eeaf5 |
730 | has '+message' => (default => 'Hello I am My::Foo'); |
731 | |
1cd45431 |
732 | What is happening here is that B<My::Foo> is cloning the C<message> attribute |
733 | from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt> |
734 | 'Str'> characteristics, but changing the value in C<default>. |
cd7eeaf5 |
735 | |
8d62bf6d |
736 | Here is another example, but within the context of a role: |
737 | |
738 | package Foo::Role; |
739 | use Moose::Role; |
986d175a |
740 | |
8d62bf6d |
741 | has 'message' => ( |
742 | is => 'rw', |
743 | isa => 'Str', |
744 | default => 'Hello, I am a Foo' |
745 | ); |
986d175a |
746 | |
8d62bf6d |
747 | package My::Foo; |
748 | use Moose; |
986d175a |
749 | |
8d62bf6d |
750 | with 'Foo::Role'; |
986d175a |
751 | |
8d62bf6d |
752 | has '+message' => (default => 'Hello I am My::Foo'); |
753 | |
d03bd989 |
754 | In this case, we are basically taking the attribute which the role supplied |
755 | and altering it within the bounds of this feature. |
8d62bf6d |
756 | |
73f70bdf |
757 | Note that you can only extend an attribute from either a superclass or a role, |
758 | you cannot extend an attribute in a role that composes over an attribute from |
759 | another role. |
760 | |
d03bd989 |
761 | Aside from where the attributes come from (one from superclass, the other |
762 | from a role), this feature works exactly the same. This feature is restricted |
763 | somewhat, so as to try and force at least I<some> sanity into it. You are only |
4032c9bb |
764 | allowed to change the following attributes: |
cd7eeaf5 |
765 | |
766 | =over 4 |
767 | |
26fbace8 |
768 | =item I<default> |
cd7eeaf5 |
769 | |
770 | Change the default value of an attribute. |
771 | |
26fbace8 |
772 | =item I<coerce> |
cd7eeaf5 |
773 | |
774 | Change whether the attribute attempts to coerce a value passed to it. |
775 | |
26fbace8 |
776 | =item I<required> |
cd7eeaf5 |
777 | |
778 | Change if the attribute is required to have a value. |
779 | |
780 | =item I<documentation> |
781 | |
782 | Change the documentation string associated with the attribute. |
783 | |
83cc9094 |
784 | =item I<lazy> |
785 | |
786 | Change if the attribute lazily initializes the slot. |
787 | |
cd7eeaf5 |
788 | =item I<isa> |
789 | |
d03bd989 |
790 | You I<are> allowed to change the type without restriction. |
aed87761 |
791 | |
d03bd989 |
792 | It is recommended that you use this freedom with caution. We used to |
793 | only allow for extension only if the type was a subtype of the parent's |
794 | type, but we felt that was too restrictive and is better left as a |
795 | policy decision. |
cd7eeaf5 |
796 | |
83cc9094 |
797 | =item I<handles> |
798 | |
26fbace8 |
799 | You are allowed to B<add> a new C<handles> definition, but you are B<not> |
800 | allowed to I<change> one. |
83cc9094 |
801 | |
8d62bf6d |
802 | =item I<builder> |
803 | |
804 | You are allowed to B<add> a new C<builder> definition, but you are B<not> |
805 | allowed to I<change> one. |
806 | |
13284479 |
807 | =item I<metaclass> |
808 | |
809 | You are allowed to B<add> a new C<metaclass> definition, but you are |
810 | B<not> allowed to I<change> one. |
811 | |
812 | =item I<traits> |
813 | |
814 | You are allowed to B<add> additional traits to the C<traits> definition. |
6549b0d1 |
815 | These traits will be composed into the attribute, but preexisting traits |
13284479 |
816 | B<are not> overridden, or removed. |
817 | |
cd7eeaf5 |
818 | =back |
819 | |
78946cf8 |
820 | =item B<before $name|@names|\@names|qr/.../ =E<gt> sub { ... }> |
6ba6d68c |
821 | |
78946cf8 |
822 | =item B<after $name|@names|\@names|qr/.../ =E<gt> sub { ... }> |
6ba6d68c |
823 | |
78946cf8 |
824 | =item B<around $name|@names|\@names|qr/.../ =E<gt> sub { ... }> |
6ba6d68c |
825 | |
e9f7d5c5 |
826 | These three items are syntactic sugar for the before, after, and around method |
d8af92ae |
827 | modifier features that L<Class::MOP> provides. More information on these may be |
9b75e4b6 |
828 | found in L<Moose::Manual::MethodModifiers> and the |
829 | L<Class::MOP::Class documentation|Class::MOP::Class/"Method Modifiers">. |
6ba6d68c |
830 | |
159da176 |
831 | =item B<super> |
832 | |
26fbace8 |
833 | The keyword C<super> is a no-op when called outside of an C<override> method. In |
834 | the context of an C<override> method, it will call the next most appropriate |
159da176 |
835 | superclass method with the same arguments as the original method. |
836 | |
837 | =item B<override ($name, &sub)> |
838 | |
26fbace8 |
839 | An C<override> method is a way of explicitly saying "I am overriding this |
840 | method from my superclass". You can call C<super> within this method, and |
841 | it will work as expected. The same thing I<can> be accomplished with a normal |
842 | method call and the C<SUPER::> pseudo-package; it is really your choice. |
159da176 |
843 | |
844 | =item B<inner> |
845 | |
26fbace8 |
846 | The keyword C<inner>, much like C<super>, is a no-op outside of the context of |
847 | an C<augment> method. You can think of C<inner> as being the inverse of |
68efb014 |
848 | C<super>; the details of how C<inner> and C<augment> work is best described in |
5cfe3805 |
849 | the L<Moose::Cookbook::Basics::Recipe6>. |
159da176 |
850 | |
851 | =item B<augment ($name, &sub)> |
852 | |
26fbace8 |
853 | An C<augment> method, is a way of explicitly saying "I am augmenting this |
854 | method from my superclass". Once again, the details of how C<inner> and |
5cfe3805 |
855 | C<augment> work is best described in the L<Moose::Cookbook::Basics::Recipe6>. |
159da176 |
856 | |
6ba6d68c |
857 | =item B<confess> |
858 | |
68efb014 |
859 | This is the C<Carp::confess> function, and exported here because I use it |
d03bd989 |
860 | all the time. |
6ba6d68c |
861 | |
862 | =item B<blessed> |
863 | |
edd0727e |
864 | This is the C<Scalar::Util::blessed> function. It is exported here because I |
26fbace8 |
865 | use it all the time. It is highly recommended that this is used instead of |
6ba6d68c |
866 | C<ref> anywhere you need to test for an object's class name. |
867 | |
868 | =back |
869 | |
c1381000 |
870 | =head1 METACLASS |
54f2996d |
871 | |
c1381000 |
872 | When you use Moose, you can specify which metaclass to use: |
873 | |
874 | use Moose -metaclass => 'My::Meta::Class'; |
875 | |
876 | You can also specify traits which will be applied to your metaclass: |
54f2996d |
877 | |
878 | use Moose -traits => 'My::Trait'; |
879 | |
880 | This is very similar to the attribute traits feature. When you do |
881 | this, your class's C<meta> object will have the specified traits |
8a8856de |
882 | applied to it. See L<Metaclass and Trait Name Resolution> for more |
883 | details. |
54f2996d |
884 | |
8a8856de |
885 | =head2 Metaclass and Trait Name Resolution |
54f2996d |
886 | |
887 | By default, when given a trait name, Moose simply tries to load a |
888 | class of the same name. If such a class does not exist, it then looks |
889 | for for a class matching |
890 | B<Moose::Meta::$type::Custom::Trait::$trait_name>. The C<$type> |
891 | variable here will be one of B<Attribute> or B<Class>, depending on |
892 | what the trait is being applied to. |
893 | |
894 | If a class with this long name exists, Moose checks to see if it has |
895 | the method C<register_implementation>. This method is expected to |
896 | return the I<real> class name of the trait. If there is no |
897 | C<register_implementation> method, it will fall back to using |
898 | B<Moose::Meta::$type::Custom::Trait::$trait> as the trait name. |
899 | |
8a8856de |
900 | The lookup method for metaclasses is the same, except that it looks |
901 | for a class matching B<Moose::Meta::$type::Custom::$metaclass_name>. |
902 | |
54f2996d |
903 | If all this is confusing, take a look at |
904 | L<Moose::Cookbook::Meta::Recipe3>, which demonstrates how to create an |
905 | attribute trait. |
906 | |
1cd45431 |
907 | =head1 UNIMPORTING FUNCTIONS |
31f8ec72 |
908 | |
909 | =head2 B<unimport> |
910 | |
1cd45431 |
911 | Moose offers a way to remove the keywords it exports, through the C<unimport> |
31f8ec72 |
912 | method. You simply have to say C<no Moose> at the bottom of your code for this |
913 | to work. Here is an example: |
914 | |
915 | package Person; |
916 | use Moose; |
917 | |
918 | has 'first_name' => (is => 'rw', isa => 'Str'); |
919 | has 'last_name' => (is => 'rw', isa => 'Str'); |
26fbace8 |
920 | |
921 | sub full_name { |
31f8ec72 |
922 | my $self = shift; |
26fbace8 |
923 | $self->first_name . ' ' . $self->last_name |
31f8ec72 |
924 | } |
26fbace8 |
925 | |
926 | no Moose; # keywords are removed from the Person package |
31f8ec72 |
927 | |
9bcfbab1 |
928 | =head1 EXTENDING AND EMBEDDING MOOSE |
929 | |
5e86efbe |
930 | To learn more about extending Moose, we recommend checking out the |
931 | "Extending" recipes in the L<Moose::Cookbook>, starting with |
932 | L<Moose::Cookbook::Extending::Recipe1>, which provides an overview of |
933 | all the different ways you might extend Moose. |
554b7648 |
934 | |
935 | =head2 B<< Moose->init_meta(for_class => $class, base_class => $baseclass, metaclass => $metaclass) >> |
9bcfbab1 |
936 | |
554b7648 |
937 | The C<init_meta> method sets up the metaclass object for the class |
b143539e |
938 | specified by C<for_class>. This method injects a a C<meta> accessor |
939 | into the class so you can get at this object. It also sets the class's |
554b7648 |
940 | superclass to C<base_class>, with L<Moose::Object> as the default. |
9bcfbab1 |
941 | |
a8de959b |
942 | C<init_meta> returns the metaclass object for C<$class>. |
943 | |
16fb3624 |
944 | You can specify an alternate metaclass with the C<metaclass> option. |
26fbace8 |
945 | |
80837fe1 |
946 | For more detail on this topic, see L<Moose::Cookbook::Extending::Recipe2>. |
947 | |
554b7648 |
948 | This method used to be documented as a function which accepted |
949 | positional parameters. This calling style will still work for |
4a66a4b3 |
950 | backwards compatibility, but is deprecated. |
554b7648 |
951 | |
952 | =head2 B<import> |
953 | |
954 | Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}> |
955 | and C<{into_level =E<gt> 1}>. |
956 | |
957 | B<NOTE>: Doing this is more or less deprecated. Use L<Moose::Exporter> |
958 | instead, which lets you stack multiple C<Moose.pm>-alike modules |
959 | sanely. It handles getting the exported functions into the right place |
960 | for you. |
961 | |
23d3fe84 |
962 | =head2 B<throw_error> |
4c0b3599 |
963 | |
edd0727e |
964 | An alias for C<confess>, used internally by Moose. |
4c0b3599 |
965 | |
a94f30ac |
966 | =head2 The MooseX:: namespace |
967 | |
968 | Generally if you're writing an extension I<for> Moose itself you'll want |
969 | to put your extension in the C<MooseX::> namespace. This namespace is |
970 | specifically for extensions that make Moose better or different in some |
971 | fundamental way. It is traditionally B<not> for a package that just happens |
972 | to use Moose. This namespace follows from the examples of the C<LWPx::> |
973 | and C<DBIx::> namespaces that perform the same function for C<LWP> and C<DBI> |
974 | respectively. |
975 | |
6ea5491a |
976 | =head1 METACLASS COMPATIBILITY AND MOOSE |
977 | |
978 | Metaclass compatibility is a thorny subject. You should start by |
979 | reading the "About Metaclass compatibility" section in the |
980 | C<Class::MOP> docs. |
981 | |
982 | Moose will attempt to resolve a few cases of metaclass incompatibility |
b9216044 |
983 | when you set the superclasses for a class, in addition to the cases that |
984 | C<Class::MOP> handles. |
985 | |
986 | Moose tries to determine if the metaclasses only "differ by roles". This |
987 | means that the parent and child's metaclass share a common ancestor in |
988 | their respective hierarchies, and that the subclasses under the common |
989 | ancestor are only different because of role applications. This case is |
990 | actually fairly common when you mix and match various C<MooseX::*> |
991 | modules, many of which apply roles to the metaclass. |
6ea5491a |
992 | |
993 | If the parent and child do differ by roles, Moose replaces the |
994 | metaclass in the child with a newly created metaclass. This metaclass |
edd0727e |
995 | is a subclass of the parent's metaclass which does all of the roles that |
6ea5491a |
996 | the child's metaclass did before being replaced. Effectively, this |
997 | means the new metaclass does all of the roles done by both the |
998 | parent's and child's original metaclasses. |
999 | |
1000 | Ultimately, this is all transparent to you except in the case of an |
1001 | unresolvable conflict. |
1002 | |
05d9eaf6 |
1003 | =head1 CAVEATS |
1004 | |
1005 | =over 4 |
1006 | |
1007 | =item * |
1008 | |
1cd45431 |
1009 | It should be noted that C<super> and C<inner> B<cannot> be used in the same |
1010 | method. However, they may be combined within the same class hierarchy; see |
1011 | F<t/014_override_augment_inner_super.t> for an example. |
05d9eaf6 |
1012 | |
26fbace8 |
1013 | The reason for this is that C<super> is only valid within a method |
1014 | with the C<override> modifier, and C<inner> will never be valid within an |
1015 | C<override> method. In fact, C<augment> will skip over any C<override> methods |
68efb014 |
1016 | when searching for its appropriate C<inner>. |
05d9eaf6 |
1017 | |
1cd45431 |
1018 | This might seem like a restriction, but I am of the opinion that keeping these |
1019 | two features separate (yet interoperable) actually makes them easy to use, since |
1020 | their behavior is then easier to predict. Time will tell whether I am right or |
c84f324f |
1021 | not (UPDATE: so far so good). |
05d9eaf6 |
1022 | |
9b9da6f1 |
1023 | =back |
1024 | |
e49c11d2 |
1025 | =head1 GETTING HELP |
1026 | |
1027 | We offer both a mailing list and a very active IRC channel. |
1028 | |
1029 | The mailing list is L<moose@perl.org>. You must be subscribed to send |
1030 | a message. To subscribe, send an empty message to |
1031 | L<moose-subscribe@perl.org> |
1032 | |
236b8a02 |
1033 | You can also visit us at C<#moose> on L<irc://irc.perl.org/#moose> |
60cbb35f |
1034 | This channel is quite active, and questions at all levels (on Moose-related |
1035 | topics ;) are welcome. |
e49c11d2 |
1036 | |
5569c072 |
1037 | =head1 ACKNOWLEDGEMENTS |
1038 | |
1039 | =over 4 |
1040 | |
54c189df |
1041 | =item I blame Sam Vilain for introducing me to the insanity that is meta-models. |
5569c072 |
1042 | |
54c189df |
1043 | =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6. |
5569c072 |
1044 | |
26fbace8 |
1045 | =item Without Yuval "nothingmuch" Kogman this module would not be possible, |
54c189df |
1046 | and it certainly wouldn't have this name ;P |
5569c072 |
1047 | |
26fbace8 |
1048 | =item The basis of the TypeContraints module was Rob Kinyon's idea |
5569c072 |
1049 | originally, I just ran with it. |
1050 | |
638585e1 |
1051 | =item Thanks to mst & chansen and the whole #moose posse for all the |
c84f324f |
1052 | early ideas/feature-requests/encouragement/bug-finding. |
d46a48f3 |
1053 | |
68efb014 |
1054 | =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes. |
1055 | |
5569c072 |
1056 | =back |
1057 | |
e90c03d0 |
1058 | =head1 SEE ALSO |
1059 | |
1060 | =over 4 |
1061 | |
c84f324f |
1062 | =item L<http://www.iinteractive.com/moose> |
1063 | |
6d137156 |
1064 | This is the official web home of Moose, it contains links to our public git repository |
26fbace8 |
1065 | as well as links to a number of talks and articles on Moose and Moose related |
1066 | technologies. |
c84f324f |
1067 | |
196064ab |
1068 | =item The Moose is flying, a tutorial by Randal Schwartz |
1069 | |
1070 | Part 1 - L<http://www.stonehenge.com/merlyn/LinuxMag/col94.html> |
1071 | |
1072 | Part 2 - L<http://www.stonehenge.com/merlyn/LinuxMag/col95.html> |
1073 | |
12aed9a0 |
1074 | =item Several Moose extension modules in the C<MooseX::> namespace. |
1075 | |
1076 | See L<http://search.cpan.org/search?query=MooseX::> for extensions. |
28669f89 |
1077 | |
e49c11d2 |
1078 | =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/moose> |
1079 | |
c84f324f |
1080 | =back |
1081 | |
004222dc |
1082 | =head2 Books |
1083 | |
1084 | =over 4 |
1085 | |
1086 | =item The Art of the MetaObject Protocol |
1087 | |
edd0727e |
1088 | I mention this in the L<Class::MOP> docs too, as this book was critical in |
004222dc |
1089 | the development of both modules and is highly recommended. |
1090 | |
1091 | =back |
1092 | |
26fbace8 |
1093 | =head2 Papers |
c84f324f |
1094 | |
1095 | =over 4 |
e90c03d0 |
1096 | |
159da176 |
1097 | =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf> |
1098 | |
26fbace8 |
1099 | This paper (suggested by lbr on #moose) was what lead to the implementation |
1100 | of the C<super>/C<override> and C<inner>/C<augment> features. If you really |
1cd45431 |
1101 | want to understand them, I suggest you read this. |
159da176 |
1102 | |
e90c03d0 |
1103 | =back |
1104 | |
fcd84ca9 |
1105 | =head1 BUGS |
1106 | |
26fbace8 |
1107 | All complex software has bugs lurking in it, and this module is no |
7efc4307 |
1108 | exception. |
1109 | |
1110 | Please report any bugs to C<bug-moose@rt.cpan.org>, or through the web |
1111 | interface at L<http://rt.cpan.org>. |
fcd84ca9 |
1112 | |
0334ee02 |
1113 | You can also discuss feature requests or possible bugs on the Moose mailing |
1114 | list (moose@perl.org) or on IRC at L<irc://irc.perl.org/#moose>. |
1115 | |
47b19570 |
1116 | =head1 FEATURE REQUESTS |
1117 | |
d03bd989 |
1118 | We are very strict about what features we add to the Moose core, especially |
1119 | the user-visible features. Instead we have made sure that the underlying |
1120 | meta-system of Moose is as extensible as possible so that you can add your |
854b298d |
1121 | own features easily. |
1122 | |
1123 | That said, occasionally there is a feature needed in the meta-system |
1124 | to support your planned extension, in which case you should either |
1125 | email the mailing list (moose@perl.org) or join us on IRC at |
1126 | L<irc://irc.perl.org/#moose> to discuss. The |
1127 | L<Moose::Manual::Contributing> has more detail about how and when you |
1128 | can contribute. |
47b19570 |
1129 | |
ad46f524 |
1130 | =head1 CABAL |
862ae2c4 |
1131 | |
ad46f524 |
1132 | There are only a few people with the rights to release a new version |
862ae2c4 |
1133 | of Moose. The Moose Cabal are the people to go to with questions regarding |
ad46f524 |
1134 | the wider purview of Moose. They help maintain not just the code |
958dc4e3 |
1135 | but the community as well. |
862ae2c4 |
1136 | |
1137 | Stevan (stevan) Little E<lt>stevan@iinteractive.comE<gt> |
1138 | |
2a267bff |
1139 | Jesse (doy) Luehrs E<lt>doy at tozt dot netE<gt> |
1140 | |
862ae2c4 |
1141 | Yuval (nothingmuch) Kogman |
1142 | |
69ba075f |
1143 | Shawn (sartak) Moore E<lt>sartak@bestpractical.comE<gt> |
862ae2c4 |
1144 | |
fd995afb |
1145 | Hans Dieter (confound) Pearcey E<lt>hdp@pobox.comE<gt> |
1146 | |
d209e3ad |
1147 | Chris (perigrin) Prather |
1148 | |
36edf31b |
1149 | Florian Ragwitz E<lt>rafl@debian.orgE<gt> |
d209e3ad |
1150 | |
2a267bff |
1151 | Dave (autarch) Rolsky E<lt>autarch@urth.orgE<gt> |
1152 | |
ad46f524 |
1153 | =head1 CONTRIBUTORS |
db1ab48d |
1154 | |
9af1d28b |
1155 | Aankhen |
1156 | |
1157 | Adam (Alias) Kennedy |
1158 | |
1159 | Anders (Debolaz) Nor Berle |
1160 | |
ad46f524 |
1161 | Chris (perigrin) Prather |
5868294f |
1162 | |
9af1d28b |
1163 | Christian (chansen) Hansen |
1164 | |
ad46f524 |
1165 | Cory (gphat) Watson |
1166 | |
1167 | Dylan Hardison (doc fixes) |
1168 | |
9af1d28b |
1169 | Eric (ewilhelm) Wilhelm |
1170 | |
ad46f524 |
1171 | Evan Carroll |
1172 | |
1173 | Florian (rafl) Ragwitz |
1174 | |
9af1d28b |
1175 | Guillermo (groditi) Roditi |
1176 | |
ad46f524 |
1177 | Jason May |
1178 | |
1179 | Jay Hannah |
1180 | |
9af1d28b |
1181 | Jess (castaway) Robinson |
1182 | |
ad46f524 |
1183 | Jonathan (jrockway) Rockway |
9af1d28b |
1184 | |
ad46f524 |
1185 | Matt (mst) Trout |
9af1d28b |
1186 | |
ad46f524 |
1187 | Nathan (kolibrie) Gray |
9af1d28b |
1188 | |
ad46f524 |
1189 | Paul (frodwith) Driver |
9af1d28b |
1190 | |
ad46f524 |
1191 | Piotr (dexter) Roszatycki |
f44ae52f |
1192 | |
ad46f524 |
1193 | Robert Buels |
68b6146c |
1194 | |
ad46f524 |
1195 | Robert (phaylon) Sedlacek |
e46f5cc2 |
1196 | |
ad46f524 |
1197 | Robert (rlb3) Boone |
3ccdc84a |
1198 | |
26fbace8 |
1199 | Sam (mugwump) Vilain |
f1917f58 |
1200 | |
ad46f524 |
1201 | Scott (konobi) McWhirter |
2f7e4042 |
1202 | |
ad46f524 |
1203 | Shawn (Sartak) Moore |
0be258b5 |
1204 | |
ad46f524 |
1205 | Shlomi (rindolf) Fish |
fcd84ca9 |
1206 | |
ad46f524 |
1207 | Tom (dec) Lanyon |
fcd84ca9 |
1208 | |
ad46f524 |
1209 | Wallace (wreis) Reis |
fcd84ca9 |
1210 | |
ad46f524 |
1211 | ... and many other #moose folks |
fcd84ca9 |
1212 | |
ddd0ec20 |
1213 | =cut |