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