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