Commit | Line | Data |
fcd84ca9 |
1 | |
2 | package Moose; |
3 | |
4 | use strict; |
5 | use warnings; |
6 | |
ecb1297a |
7 | use 5.008; |
8 | |
6eacdaea |
9 | our $VERSION = '0.58'; |
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 | |
cbac012a |
18 | use Class::MOP 0.67; |
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 | |
5bd4db9b |
127 | sub make_immutable { |
97a93056 |
128 | my $class = shift; |
5bd4db9b |
129 | cluck "The make_immutable keyword has been deprecated, " . |
130 | "please go back to __PACKAGE__->meta->make_immutable\n"; |
aedcb7d9 |
131 | Class::MOP::Class->initialize($class)->make_immutable(@_); |
5bd4db9b |
132 | } |
9bcfbab1 |
133 | |
aedcb7d9 |
134 | Moose::Exporter->setup_import_methods( |
97a93056 |
135 | with_caller => [ |
136 | qw( extends with has before after around override augment make_immutable ) |
137 | ], |
138 | as_is => [ |
139 | qw( super inner ), |
5bd4db9b |
140 | \&Carp::confess, |
141 | \&Scalar::Util::blessed, |
142 | ], |
143 | ); |
144 | |
cc841c0e |
145 | sub init_meta { |
085fba61 |
146 | # This used to be called as a function. This hack preserves |
147 | # backwards compatibility. |
148 | if ( $_[0] ne __PACKAGE__ ) { |
149 | return __PACKAGE__->init_meta( |
150 | for_class => $_[0], |
151 | base_class => $_[1], |
152 | metaclass => $_[2], |
153 | ); |
154 | } |
7c4676ef |
155 | |
0338a411 |
156 | shift; |
157 | my %args = @_; |
158 | |
159 | my $class = $args{for_class} |
c245d69b |
160 | or Moose->throw_error("Cannot call init_meta without specifying a for_class"); |
085fba61 |
161 | my $base_class = $args{base_class} || 'Moose::Object'; |
162 | my $metaclass = $args{metaclass} || 'Moose::Meta::Class'; |
cc841c0e |
163 | |
c245d69b |
164 | Moose->throw_error("The Metaclass $metaclass must be a subclass of Moose::Meta::Class.") |
cc841c0e |
165 | unless $metaclass->isa('Moose::Meta::Class'); |
166 | |
167 | # make a subtype for each Moose class |
168 | class_type($class) |
169 | unless find_type_constraint($class); |
170 | |
171 | my $meta; |
50d5df60 |
172 | |
173 | if ( $meta = Class::MOP::get_metaclass_by_name($class) ) { |
174 | unless ( $meta->isa("Moose::Meta::Class") ) { |
c245d69b |
175 | Moose->throw_error("$class already has a metaclass, but it does not inherit $metaclass ($meta)"); |
50d5df60 |
176 | } |
177 | } else { |
178 | # no metaclass, no 'meta' method |
179 | |
180 | # now we check whether our ancestors have metaclass, and if so borrow that |
181 | my ( undef, @isa ) = @{ $class->mro::get_linear_isa }; |
182 | |
183 | foreach my $ancestor ( @isa ) { |
184 | my $ancestor_meta = Class::MOP::get_metaclass_by_name($ancestor) || next; |
185 | |
186 | my $ancestor_meta_class = ($ancestor_meta->is_immutable |
187 | ? $ancestor_meta->get_mutable_metaclass_name |
188 | : ref($ancestor_meta)); |
189 | |
190 | # if we have an ancestor metaclass that inherits $metaclass, we use |
41419b9e |
191 | # that. This is like _fix_metaclass_incompatibility, but we can do it now. |
50d5df60 |
192 | |
193 | # the case of having an ancestry is not very common, but arises in |
194 | # e.g. Reaction |
195 | unless ( $metaclass->isa( $ancestor_meta_class ) ) { |
196 | if ( $ancestor_meta_class->isa($metaclass) ) { |
197 | $metaclass = $ancestor_meta_class; |
198 | } |
199 | } |
200 | } |
201 | |
202 | $meta = $metaclass->initialize($class); |
203 | } |
204 | |
cc841c0e |
205 | if ( $class->can('meta') ) { |
50d5df60 |
206 | # check 'meta' method |
207 | |
208 | # it may be inherited |
209 | |
cc841c0e |
210 | # NOTE: |
211 | # this is the case where the metaclass pragma |
212 | # was used before the 'use Moose' statement to |
213 | # override a specific class |
50d5df60 |
214 | my $method_meta = $class->meta; |
215 | |
216 | ( blessed($method_meta) && $method_meta->isa('Moose::Meta::Class') ) |
c245d69b |
217 | || Moose->throw_error("$class already has a &meta function, but it does not return a Moose::Meta::Class ($meta)"); |
50d5df60 |
218 | |
219 | $meta = $method_meta; |
cc841c0e |
220 | } |
50d5df60 |
221 | |
222 | unless ( $meta->has_method("meta") ) { # don't overwrite |
223 | # also check for inherited non moose 'meta' method? |
224 | # FIXME also skip this if the user requested by passing an option |
cc841c0e |
225 | $meta->add_method( |
226 | 'meta' => sub { |
227 | # re-initialize so it inherits properly |
50d5df60 |
228 | $metaclass->initialize( ref($_[0]) || $_[0] ); |
cc841c0e |
229 | } |
230 | ); |
231 | } |
232 | |
233 | # make sure they inherit from Moose::Object |
234 | $meta->superclasses($base_class) |
235 | unless $meta->superclasses(); |
236 | |
237 | return $meta; |
238 | } |
239 | |
085fba61 |
240 | # This may be used in some older MooseX extensions. |
241 | sub _get_caller { |
242 | goto &Moose::Exporter::_get_caller; |
243 | } |
244 | |
8ecb1fa0 |
245 | ## make 'em all immutable |
246 | |
247 | $_->meta->make_immutable( |
0779da92 |
248 | inline_constructor => 1, |
249 | constructor_name => "_new", |
77a18c28 |
250 | inline_accessors => 1, # these are Class::MOP accessors, so they need inlining |
9bcfbab1 |
251 | ) |
0779da92 |
252 | for (qw( |
253 | Moose::Meta::Attribute |
254 | Moose::Meta::Class |
255 | Moose::Meta::Instance |
256 | |
257 | Moose::Meta::TypeConstraint |
258 | Moose::Meta::TypeConstraint::Union |
259 | Moose::Meta::TypeConstraint::Parameterized |
9ad786af |
260 | Moose::Meta::TypeConstraint::Parameterizable |
0779da92 |
261 | Moose::Meta::TypeConstraint::Enum |
262 | Moose::Meta::TypeConstraint::Class |
263 | Moose::Meta::TypeConstraint::Role |
264 | Moose::Meta::TypeConstraint::Registry |
265 | Moose::Meta::TypeCoercion |
266 | Moose::Meta::TypeCoercion::Union |
267 | |
268 | Moose::Meta::Method |
269 | Moose::Meta::Method::Accessor |
270 | Moose::Meta::Method::Constructor |
271 | Moose::Meta::Method::Destructor |
272 | Moose::Meta::Method::Overriden |
273 | Moose::Meta::Method::Augmented |
274 | |
275 | Moose::Meta::Role |
276 | Moose::Meta::Role::Method |
277 | Moose::Meta::Role::Method::Required |
278 | |
279 | Moose::Meta::Role::Composite |
280 | |
281 | Moose::Meta::Role::Application |
282 | Moose::Meta::Role::Application::RoleSummation |
283 | Moose::Meta::Role::Application::ToClass |
284 | Moose::Meta::Role::Application::ToRole |
285 | Moose::Meta::Role::Application::ToInstance |
0779da92 |
286 | )); |
8ecb1fa0 |
287 | |
fcd84ca9 |
288 | 1; |
289 | |
290 | __END__ |
291 | |
292 | =pod |
293 | |
294 | =head1 NAME |
295 | |
8bdc7f13 |
296 | Moose - A postmodern object system for Perl 5 |
fcd84ca9 |
297 | |
298 | =head1 SYNOPSIS |
e522431d |
299 | |
300 | package Point; |
1cd45431 |
301 | use Moose; # automatically turns on strict and warnings |
26fbace8 |
302 | |
43d599e5 |
303 | has 'x' => (is => 'rw', isa => 'Int'); |
304 | has 'y' => (is => 'rw', isa => 'Int'); |
26fbace8 |
305 | |
e522431d |
306 | sub clear { |
307 | my $self = shift; |
308 | $self->x(0); |
26fbace8 |
309 | $self->y(0); |
e522431d |
310 | } |
26fbace8 |
311 | |
e522431d |
312 | package Point3D; |
313 | use Moose; |
26fbace8 |
314 | |
e522431d |
315 | extends 'Point'; |
26fbace8 |
316 | |
43d599e5 |
317 | has 'z' => (is => 'rw', isa => 'Int'); |
26fbace8 |
318 | |
e522431d |
319 | after 'clear' => sub { |
320 | my $self = shift; |
43d599e5 |
321 | $self->z(0); |
26fbace8 |
322 | }; |
2c0cbef7 |
323 | |
fcd84ca9 |
324 | =head1 DESCRIPTION |
325 | |
26fbace8 |
326 | Moose is an extension of the Perl 5 object system. |
e522431d |
327 | |
9b9da6f1 |
328 | The main goal of Moose is to make Perl 5 Object Oriented programming |
329 | easier, more consistent and less tedious. With Moose you can to think |
6f894f30 |
330 | more about what you want to do and less about the mechanics of OOP. |
fcd84ca9 |
331 | |
6f894f30 |
332 | Additionally, Moose is built on top of L<Class::MOP>, which is a |
333 | metaclass system for Perl 5. This means that Moose not only makes |
334 | building normal Perl 5 objects better, but it provides the power of |
335 | metaclass programming as well. |
8bdc7f13 |
336 | |
f5909dca |
337 | =head2 New to Moose? |
338 | |
6f894f30 |
339 | If you're new to Moose, the best place to start is the L<Moose::Intro> |
340 | docs, followed by the L<Moose::Cookbook>. The intro will show you what |
341 | Moose is, and how it makes Perl 5 OO better. |
342 | |
343 | The cookbook recipes on Moose basics will get you up to speed with |
344 | many of Moose's features quickly. Once you have an idea of what Moose |
345 | can do, you can use the API documentation to get more detail on |
346 | features which interest you. |
f5909dca |
347 | |
28669f89 |
348 | =head2 Moose Extensions |
349 | |
12aed9a0 |
350 | The C<MooseX::> namespace is the official place to find Moose extensions. |
351 | These extensions can be found on the CPAN. The easiest way to find them |
352 | is to search for them (L<http://search.cpan.org/search?query=MooseX::>), |
353 | or to examine L<Task::Moose> which aims to keep an up-to-date, easily |
354 | installable list of Moose extensions. |
28669f89 |
355 | |
6ba6d68c |
356 | =head1 BUILDING CLASSES WITH MOOSE |
357 | |
68efb014 |
358 | Moose makes every attempt to provide as much convenience as possible during |
359 | class construction/definition, but still stay out of your way if you want it |
360 | to. Here are a few items to note when building classes with Moose. |
6ba6d68c |
361 | |
26fbace8 |
362 | Unless specified with C<extends>, any class which uses Moose will |
6ba6d68c |
363 | inherit from L<Moose::Object>. |
364 | |
1cd45431 |
365 | Moose will also manage all attributes (including inherited ones) that are |
366 | defined with C<has>. And (assuming you call C<new>, which is inherited from |
367 | L<Moose::Object>) this includes properly initializing all instance slots, |
368 | setting defaults where appropriate, and performing any type constraint checking |
369 | or coercion. |
6ba6d68c |
370 | |
004222dc |
371 | =head1 PROVIDED METHODS |
6ba6d68c |
372 | |
004222dc |
373 | Moose provides a number of methods to all your classes, mostly through the |
374 | inheritance of L<Moose::Object>. There is however, one exception. |
6ba6d68c |
375 | |
376 | =over 4 |
377 | |
378 | =item B<meta> |
379 | |
380 | This is a method which provides access to the current class's metaclass. |
381 | |
004222dc |
382 | =back |
383 | |
384 | =head1 EXPORTED FUNCTIONS |
385 | |
386 | Moose will export a number of functions into the class's namespace which |
387 | may then be used to set up the class. These functions all work directly |
388 | on the current class. |
389 | |
390 | =over 4 |
391 | |
6ba6d68c |
392 | =item B<extends (@superclasses)> |
393 | |
394 | This function will set the superclass(es) for the current class. |
395 | |
26fbace8 |
396 | This approach is recommended instead of C<use base>, because C<use base> |
397 | actually C<push>es onto the class's C<@ISA>, whereas C<extends> will |
398 | replace it. This is important to ensure that classes which do not have |
68efb014 |
399 | superclasses still properly inherit from L<Moose::Object>. |
6ba6d68c |
400 | |
43d599e5 |
401 | =item B<with (@roles)> |
e9ec68d6 |
402 | |
004222dc |
403 | This will apply a given set of C<@roles> to the local class. |
e9ec68d6 |
404 | |
cd7eeaf5 |
405 | =item B<has $name =E<gt> %options> |
6ba6d68c |
406 | |
26fbace8 |
407 | This will install an attribute of a given C<$name> into the current class. |
408 | The C<%options> are the same as those provided by |
409 | L<Class::MOP::Attribute>, in addition to the list below which are provided |
43d599e5 |
410 | by Moose (L<Moose::Meta::Attribute> to be more specific): |
6ba6d68c |
411 | |
412 | =over 4 |
413 | |
076c81ed |
414 | =item I<is =E<gt> 'rw'|'ro'> |
6ba6d68c |
415 | |
26fbace8 |
416 | The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read |
417 | only). These will create either a read/write accessor or a read-only |
6ba6d68c |
418 | accessor respectively, using the same name as the C<$name> of the attribute. |
419 | |
1b46b845 |
420 | If you need more control over how your accessors are named, you can |
421 | use the L<reader|Class::MOP::Attribute/reader>, |
422 | L<writer|Class::MOP::Attribute/writer> and |
423 | L<accessor|Class::MOP::Attribute/accessor> options inherited from |
424 | L<Class::MOP::Attribute>, however if you use those, you won't need the |
425 | I<is> option. |
6ba6d68c |
426 | |
076c81ed |
427 | =item I<isa =E<gt> $type_name> |
6ba6d68c |
428 | |
26fbace8 |
429 | The I<isa> option uses Moose's type constraint facilities to set up runtime |
430 | type checking for this attribute. Moose will perform the checks during class |
431 | construction, and within any accessors. The C<$type_name> argument must be a |
432 | string. The string may be either a class name or a type defined using |
9cca2e9e |
433 | Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints> |
c2a69ef1 |
434 | for information on how to define a new type, and how to retrieve type meta-data). |
6ba6d68c |
435 | |
daea75c9 |
436 | =item I<coerce =E<gt> (1|0)> |
437 | |
26fbace8 |
438 | This will attempt to use coercion with the supplied type constraint to change |
439 | the value passed into any accessors or constructors. You B<must> have supplied |
5cfe3805 |
440 | a type constraint in order for this to work. See L<Moose::Cookbook::Basics::Recipe5> |
1cd45431 |
441 | for an example. |
daea75c9 |
442 | |
443 | =item I<does =E<gt> $role_name> |
444 | |
26fbace8 |
445 | This will accept the name of a role which the value stored in this attribute |
daea75c9 |
446 | is expected to have consumed. |
447 | |
448 | =item I<required =E<gt> (1|0)> |
449 | |
26fbace8 |
450 | This marks the attribute as being required. This means a I<defined> value must be |
451 | supplied during class construction, and the attribute may never be set to |
452 | C<undef> with an accessor. |
daea75c9 |
453 | |
454 | =item I<weak_ref =E<gt> (1|0)> |
455 | |
68efb014 |
456 | This will tell the class to store the value of this attribute as a weakened |
457 | reference. If an attribute is a weakened reference, it B<cannot> also be |
458 | coerced. |
daea75c9 |
459 | |
460 | =item I<lazy =E<gt> (1|0)> |
461 | |
26fbace8 |
462 | This will tell the class to not create this slot until absolutely necessary. |
daea75c9 |
463 | If an attribute is marked as lazy it B<must> have a default supplied. |
464 | |
9e93dd19 |
465 | =item I<auto_deref =E<gt> (1|0)> |
466 | |
26fbace8 |
467 | This tells the accessor whether to automatically dereference the value returned. |
1cd45431 |
468 | This is only legal if your C<isa> option is either C<ArrayRef> or C<HashRef>. |
9e93dd19 |
469 | |
65e14c86 |
470 | =item I<trigger =E<gt> $code> |
471 | |
472 | The I<trigger> option is a CODE reference which will be called after the value of |
473 | the attribute is set. The CODE ref will be passed the instance itself, the |
474 | updated value and the attribute meta-object (this is for more advanced fiddling |
475 | and can typically be ignored). You B<cannot> have a trigger on a read-only |
010997ca |
476 | attribute. |
477 | |
478 | B<NOTE:> Triggers will only fire when you B<assign> to the attribute, |
479 | either in the constructor, or using the writer. Default and built values will |
480 | B<not> cause the trigger to be fired. |
daea75c9 |
481 | |
c84f324f |
482 | =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE> |
2c0cbef7 |
483 | |
26fbace8 |
484 | The I<handles> option provides Moose classes with automated delegation features. |
485 | This is a pretty complex and powerful option. It accepts many different option |
486 | formats, each with its own benefits and drawbacks. |
38e3283b |
487 | |
1cd45431 |
488 | B<NOTE:> The class being delegated to does not need to be a Moose based class, |
489 | which is why this feature is especially useful when wrapping non-Moose classes. |
38e3283b |
490 | |
1cd45431 |
491 | All I<handles> option formats share the following traits: |
38e3283b |
492 | |
1cd45431 |
493 | You cannot override a locally defined method with a delegated method; an |
494 | exception will be thrown if you try. That is to say, if you define C<foo> in |
495 | your class, you cannot override it with a delegated C<foo>. This is almost never |
496 | something you would want to do, and if it is, you should do it by hand and not |
497 | use Moose. |
38e3283b |
498 | |
1cd45431 |
499 | You cannot override any of the methods found in Moose::Object, or the C<BUILD> |
500 | and C<DEMOLISH> methods. These will not throw an exception, but will silently |
501 | move on to the next method in the list. My reasoning for this is that you would |
502 | almost never want to do this, since it usually breaks your class. As with |
503 | overriding locally defined methods, if you do want to do this, you should do it |
504 | manually, not with Moose. |
38e3283b |
505 | |
f3c4e20e |
506 | You do not I<need> to have a reader (or accessor) for the attribute in order |
507 | to delegate to it. Moose will create a means of accessing the value for you, |
508 | however this will be several times B<less> efficient then if you had given |
509 | the attribute a reader (or accessor) to use. |
510 | |
38e3283b |
511 | Below is the documentation for each option format: |
512 | |
513 | =over 4 |
514 | |
515 | =item C<ARRAY> |
516 | |
26fbace8 |
517 | This is the most common usage for I<handles>. You basically pass a list of |
518 | method names to be delegated, and Moose will install a delegation method |
1cd45431 |
519 | for each one. |
38e3283b |
520 | |
521 | =item C<HASH> |
522 | |
26fbace8 |
523 | This is the second most common usage for I<handles>. Instead of a list of |
524 | method names, you pass a HASH ref where each key is the method name you |
525 | want installed locally, and its value is the name of the original method |
526 | in the class being delegated to. |
fd595040 |
527 | |
26fbace8 |
528 | This can be very useful for recursive classes like trees. Here is a |
5cfe3805 |
529 | quick example (soon to be expanded into a Moose::Cookbook recipe): |
38e3283b |
530 | |
1cd45431 |
531 | package Tree; |
38e3283b |
532 | use Moose; |
26fbace8 |
533 | |
38e3283b |
534 | has 'node' => (is => 'rw', isa => 'Any'); |
26fbace8 |
535 | |
38e3283b |
536 | has 'children' => ( |
537 | is => 'ro', |
538 | isa => 'ArrayRef', |
539 | default => sub { [] } |
540 | ); |
26fbace8 |
541 | |
38e3283b |
542 | has 'parent' => ( |
543 | is => 'rw', |
544 | isa => 'Tree', |
a4e516f6 |
545 | weak_ref => 1, |
38e3283b |
546 | handles => { |
547 | parent_node => 'node', |
26fbace8 |
548 | siblings => 'children', |
38e3283b |
549 | } |
550 | ); |
551 | |
1cd45431 |
552 | In this example, the Tree package gets C<parent_node> and C<siblings> methods, |
553 | which delegate to the C<node> and C<children> methods (respectively) of the Tree |
26fbace8 |
554 | instance stored in the C<parent> slot. |
38e3283b |
555 | |
556 | =item C<REGEXP> |
557 | |
26fbace8 |
558 | The regexp option works very similar to the ARRAY option, except that it builds |
559 | the list of methods for you. It starts by collecting all possible methods of the |
560 | class being delegated to, then filters that list using the regexp supplied here. |
38e3283b |
561 | |
26fbace8 |
562 | B<NOTE:> An I<isa> option is required when using the regexp option format. This |
563 | is so that we can determine (at compile time) the method list from the class. |
38e3283b |
564 | Without an I<isa> this is just not possible. |
565 | |
c84f324f |
566 | =item C<ROLE> |
567 | |
26fbace8 |
568 | With the role option, you specify the name of a role whose "interface" then |
569 | becomes the list of methods to handle. The "interface" can be defined as; the |
570 | methods of the role and any required methods of the role. It should be noted |
571 | that this does B<not> include any method modifiers or generated attribute |
c84f324f |
572 | methods (which is consistent with role composition). |
573 | |
38e3283b |
574 | =item C<CODE> |
575 | |
1cd45431 |
576 | This is the option to use when you really want to do something funky. You should |
577 | only use it if you really know what you are doing, as it involves manual |
578 | metaclass twiddling. |
38e3283b |
579 | |
1cd45431 |
580 | This takes a code reference, which should expect two arguments. The first is the |
581 | attribute meta-object this I<handles> is attached to. The second is the |
582 | metaclass of the class being delegated to. It expects you to return a hash (not |
26fbace8 |
583 | a HASH ref) of the methods you want mapped. |
38e3283b |
584 | |
585 | =back |
2c0cbef7 |
586 | |
004222dc |
587 | =item I<metaclass =E<gt> $metaclass_name> |
588 | |
589 | This tells the class to use a custom attribute metaclass for this particular |
590 | attribute. Custom attribute metaclasses are useful for extending the |
591 | capabilities of the I<has> keyword: they are the simplest way to extend the MOP, |
592 | but they are still a fairly advanced topic and too much to cover here, see |
5cfe3805 |
593 | L<Moose::Cookbook::Meta::Recipe1> for more information. |
004222dc |
594 | |
595 | The default behavior here is to just load C<$metaclass_name>; however, we also |
596 | have a way to alias to a shorter name. This will first look to see if |
597 | B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose |
598 | will then check to see if that has the method C<register_implementation>, which |
599 | should return the actual name of the custom attribute metaclass. If there is no |
600 | C<register_implementation> method, it will fall back to using |
601 | B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name. |
602 | |
603 | =item I<traits =E<gt> [ @role_names ]> |
604 | |
605 | This tells Moose to take the list of C<@role_names> and apply them to the |
606 | attribute meta-object. This is very similar to the I<metaclass> option, but |
54f2996d |
607 | allows you to use more than one extension at a time. |
004222dc |
608 | |
54f2996d |
609 | See L<TRAIT NAME RESOLUTION> for details on how a trait name is |
610 | resolved to a class name. |
611 | |
612 | Also see L<Moose::Cookbook::Meta::Recipe3> for a metaclass trait |
613 | example. |
004222dc |
614 | |
010997ca |
615 | =item I<builder> |
616 | |
1b46b845 |
617 | The value of this key is the name of the method that will be called to |
618 | obtain the value used to initialize the attribute. See the L<builder |
619 | option docs in Class::MOP::Attribute|Class::MOP::Attribute/builder> |
620 | for more information. |
010997ca |
621 | |
622 | =item I<default> |
623 | |
624 | The value of this key is the default value which will initialize the attribute. |
625 | |
1b46b845 |
626 | NOTE: If the value is a simple scalar (string or number), then it can |
627 | be just passed as is. However, if you wish to initialize it with a |
628 | HASH or ARRAY ref, then you need to wrap that inside a CODE reference. |
629 | See the L<default option docs in |
630 | Class::MOP::Attribute|Class::MOP::Attribute/default> for more |
631 | information. |
010997ca |
632 | |
633 | =item I<initializer> |
634 | |
1b46b845 |
635 | This may be a method name (referring to a method on the class with |
636 | this attribute) or a CODE ref. The initializer is used to set the |
637 | attribute value on an instance when the attribute is set during |
638 | instance initialization (but not when the value is being assigned |
639 | to). See the L<initializer option docs in |
640 | Class::MOP::Attribute|Class::MOP::Attribute/initializer> for more |
641 | information. |
010997ca |
642 | |
643 | =item I<clearer> |
644 | |
1b46b845 |
645 | Allows you to clear the value, see the L<clearer option docs in |
646 | Class::MOP::Attribute|Class::MOP::Attribute/clearer> for more |
647 | information. |
010997ca |
648 | |
649 | =item I<predicate> |
650 | |
1b46b845 |
651 | Basic test to see if a value has been set in the attribute, see the |
652 | L<predicate option docs in |
653 | Class::MOP::Attribute|Class::MOP::Attribute/predicate> for more |
654 | information. |
010997ca |
655 | |
6ba6d68c |
656 | =back |
657 | |
cd7eeaf5 |
658 | =item B<has +$name =E<gt> %options> |
659 | |
26fbace8 |
660 | This is variation on the normal attibute 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 |
739 | policy descision. |
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 | |
05d9eaf6 |
941 | =head1 CAVEATS |
942 | |
943 | =over 4 |
944 | |
945 | =item * |
946 | |
1cd45431 |
947 | It should be noted that C<super> and C<inner> B<cannot> be used in the same |
948 | method. However, they may be combined within the same class hierarchy; see |
949 | F<t/014_override_augment_inner_super.t> for an example. |
05d9eaf6 |
950 | |
26fbace8 |
951 | The reason for this is that C<super> is only valid within a method |
952 | with the C<override> modifier, and C<inner> will never be valid within an |
953 | C<override> method. In fact, C<augment> will skip over any C<override> methods |
68efb014 |
954 | when searching for its appropriate C<inner>. |
05d9eaf6 |
955 | |
1cd45431 |
956 | This might seem like a restriction, but I am of the opinion that keeping these |
957 | two features separate (yet interoperable) actually makes them easy to use, since |
958 | their behavior is then easier to predict. Time will tell whether I am right or |
c84f324f |
959 | not (UPDATE: so far so good). |
05d9eaf6 |
960 | |
9b9da6f1 |
961 | =back |
962 | |
5569c072 |
963 | =head1 ACKNOWLEDGEMENTS |
964 | |
965 | =over 4 |
966 | |
54c189df |
967 | =item I blame Sam Vilain for introducing me to the insanity that is meta-models. |
5569c072 |
968 | |
54c189df |
969 | =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6. |
5569c072 |
970 | |
26fbace8 |
971 | =item Without Yuval "nothingmuch" Kogman this module would not be possible, |
54c189df |
972 | and it certainly wouldn't have this name ;P |
5569c072 |
973 | |
26fbace8 |
974 | =item The basis of the TypeContraints module was Rob Kinyon's idea |
5569c072 |
975 | originally, I just ran with it. |
976 | |
638585e1 |
977 | =item Thanks to mst & chansen and the whole #moose posse for all the |
c84f324f |
978 | early ideas/feature-requests/encouragement/bug-finding. |
d46a48f3 |
979 | |
68efb014 |
980 | =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes. |
981 | |
5569c072 |
982 | =back |
983 | |
e90c03d0 |
984 | =head1 SEE ALSO |
985 | |
986 | =over 4 |
987 | |
c84f324f |
988 | =item L<http://www.iinteractive.com/moose> |
989 | |
990 | This is the official web home of Moose, it contains links to our public SVN repo |
26fbace8 |
991 | as well as links to a number of talks and articles on Moose and Moose related |
992 | technologies. |
c84f324f |
993 | |
196064ab |
994 | =item L<Moose::Cookbook> - How to cook a Moose |
995 | |
996 | =item The Moose is flying, a tutorial by Randal Schwartz |
997 | |
998 | Part 1 - L<http://www.stonehenge.com/merlyn/LinuxMag/col94.html> |
999 | |
1000 | Part 2 - L<http://www.stonehenge.com/merlyn/LinuxMag/col95.html> |
1001 | |
6ba6d68c |
1002 | =item L<Class::MOP> documentation |
1003 | |
1004 | =item The #moose channel on irc.perl.org |
1005 | |
e67a0fca |
1006 | =item The Moose mailing list - moose@perl.org |
1007 | |
9e0361e1 |
1008 | =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/moose> |
c84f324f |
1009 | |
12aed9a0 |
1010 | =item Several Moose extension modules in the C<MooseX::> namespace. |
1011 | |
1012 | See L<http://search.cpan.org/search?query=MooseX::> for extensions. |
28669f89 |
1013 | |
c84f324f |
1014 | =back |
1015 | |
004222dc |
1016 | =head2 Books |
1017 | |
1018 | =over 4 |
1019 | |
1020 | =item The Art of the MetaObject Protocol |
1021 | |
1022 | I mention this in the L<Class::MOP> docs too, this book was critical in |
1023 | the development of both modules and is highly recommended. |
1024 | |
1025 | =back |
1026 | |
26fbace8 |
1027 | =head2 Papers |
c84f324f |
1028 | |
1029 | =over 4 |
e90c03d0 |
1030 | |
159da176 |
1031 | =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf> |
1032 | |
26fbace8 |
1033 | This paper (suggested by lbr on #moose) was what lead to the implementation |
1034 | of the C<super>/C<override> and C<inner>/C<augment> features. If you really |
1cd45431 |
1035 | want to understand them, I suggest you read this. |
159da176 |
1036 | |
e90c03d0 |
1037 | =back |
1038 | |
fcd84ca9 |
1039 | =head1 BUGS |
1040 | |
26fbace8 |
1041 | All complex software has bugs lurking in it, and this module is no |
fcd84ca9 |
1042 | exception. If you find a bug please either email me, or add the bug |
1043 | to cpan-RT. |
1044 | |
47b19570 |
1045 | =head1 FEATURE REQUESTS |
1046 | |
1047 | We are very strict about what features we add to the Moose core, especially |
1048 | the user-visible features. Instead we have made sure that the underlying |
1049 | meta-system of Moose is as extensible as possible so that you can add your |
1050 | own features easily. That said, occasionally there is a feature needed in the |
1051 | meta-system to support your planned extension, in which case you should |
1052 | either email the mailing list or join us on irc at #moose to discuss. |
1053 | |
fcd84ca9 |
1054 | =head1 AUTHOR |
1055 | |
1056 | Stevan Little E<lt>stevan@iinteractive.comE<gt> |
1057 | |
9af1d28b |
1058 | B<with contributions from:> |
db1ab48d |
1059 | |
9af1d28b |
1060 | Aankhen |
1061 | |
1062 | Adam (Alias) Kennedy |
1063 | |
1064 | Anders (Debolaz) Nor Berle |
1065 | |
5868294f |
1066 | Nathan (kolibre) Gray |
1067 | |
9af1d28b |
1068 | Christian (chansen) Hansen |
1069 | |
e7f8d0c2 |
1070 | Hans Dieter (confound) Pearcey |
1071 | |
9af1d28b |
1072 | Eric (ewilhelm) Wilhelm |
1073 | |
1074 | Guillermo (groditi) Roditi |
1075 | |
1076 | Jess (castaway) Robinson |
1077 | |
1078 | Matt (mst) Trout |
1079 | |
1080 | Robert (phaylon) Sedlacek |
1081 | |
1082 | Robert (rlb3) Boone |
1083 | |
1084 | Scott (konobi) McWhirter |
1085 | |
f44ae52f |
1086 | Shlomi (rindolf) Fish |
1087 | |
9af1d28b |
1088 | Yuval (nothingmuch) Kogman |
1089 | |
cbe25729 |
1090 | Chris (perigrin) Prather |
1091 | |
68b6146c |
1092 | Wallace (wreis) Reis |
1093 | |
e46f5cc2 |
1094 | Jonathan (jrockway) Rockway |
1095 | |
abfdc2b4 |
1096 | Dave (autarch) Rolsky |
1097 | |
3ccdc84a |
1098 | Piotr (dexter) Roszatycki |
1099 | |
26fbace8 |
1100 | Sam (mugwump) Vilain |
f1917f58 |
1101 | |
ac211120 |
1102 | Shawn (sartak) Moore |
1103 | |
9af1d28b |
1104 | ... and many other #moose folks |
98aae381 |
1105 | |
fcd84ca9 |
1106 | =head1 COPYRIGHT AND LICENSE |
1107 | |
778db3ac |
1108 | Copyright 2006-2008 by Infinity Interactive, Inc. |
fcd84ca9 |
1109 | |
1110 | L<http://www.iinteractive.com> |
1111 | |
1112 | This library is free software; you can redistribute it and/or modify |
26fbace8 |
1113 | it under the same terms as Perl itself. |
fcd84ca9 |
1114 | |
ddd0ec20 |
1115 | =cut |