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