10 $VERSION = eval $VERSION;
11 our $AUTHORITY = 'cpan:STEVAN';
13 use Scalar::Util 'blessed';
14 use Carp 'confess', 'croak', 'cluck';
20 use Moose::Meta::Class;
21 use Moose::Meta::TypeConstraint;
22 use Moose::Meta::TypeCoercion;
23 use Moose::Meta::Attribute;
24 use Moose::Meta::Instance;
28 use Moose::Meta::Role;
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;
36 use Moose::Util::TypeConstraints;
39 BEGIN { *throw_error = \&confess } # FIXME make this smarter
44 croak "Must derive at least one class" unless @_;
47 foreach my $super (@supers) {
48 Class::MOP::load_class($super);
49 croak "You cannot inherit from a Moose Role ($super)"
50 if $super->can('meta') &&
51 blessed $super->meta &&
52 $super->meta->isa('Moose::Meta::Role')
57 # this checks the metaclass to make sure
58 # it is correct, sometimes it can get out
59 # of sync when the classes are being built
60 my $meta = Moose::Meta::Class->initialize($class)->_fix_metaclass_incompatability(@supers);
61 $meta->superclasses(@supers);
66 Moose::Util::apply_all_roles(Class::MOP::Class->initialize($class), @_);
72 croak 'Usage: has \'name\' => ( key => value, ... )' if @_ == 1;
74 my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ];
75 Class::MOP::Class->initialize($class)->add_attribute( $_, %options ) for @$attrs;
80 Moose::Util::add_method_modifier($class, 'before', \@_);
85 Moose::Util::add_method_modifier($class, 'after', \@_);
90 Moose::Util::add_method_modifier($class, 'around', \@_);
94 return unless our $SUPER_BODY; $SUPER_BODY->(our @SUPER_ARGS);
99 my ( $name, $method ) = @_;
100 Class::MOP::Class->initialize($class)->add_override_method_modifier( $name => $method );
105 our ( %INNER_BODY, %INNER_ARGS );
107 if ( my $body = $INNER_BODY{$pkg} ) {
108 my @args = @{ $INNER_ARGS{$pkg} };
109 local $INNER_ARGS{$pkg};
110 local $INNER_BODY{$pkg};
111 return $body->(@args);
119 my ( $name, $method ) = @_;
120 Class::MOP::Class->initialize($class)->add_augment_method_modifier( $name => $method );
125 cluck "The make_immutable keyword has been deprecated, " .
126 "please go back to __PACKAGE__->meta->make_immutable\n";
127 Class::MOP::Class->initialize($class)->make_immutable(@_);
130 Moose::Exporter->setup_import_methods(
132 qw( extends with has before after around override augment make_immutable )
137 \&Scalar::Util::blessed,
142 # This used to be called as a function. This hack preserves
143 # backwards compatibility.
144 if ( $_[0] ne __PACKAGE__ ) {
145 return __PACKAGE__->init_meta(
155 my $class = $args{for_class}
156 or throw_error "Cannot call init_meta without specifying a for_class";
157 my $base_class = $args{base_class} || 'Moose::Object';
158 my $metaclass = $args{metaclass} || 'Moose::Meta::Class';
161 "The Metaclass $metaclass must be a subclass of Moose::Meta::Class."
162 unless $metaclass->isa('Moose::Meta::Class');
164 # make a subtype for each Moose class
166 unless find_type_constraint($class);
170 if ( $meta = Class::MOP::get_metaclass_by_name($class) ) {
171 unless ( $meta->isa("Moose::Meta::Class") ) {
172 throw_error "$class already has a metaclass, but it does not inherit $metaclass ($meta)";
175 # no metaclass, no 'meta' method
177 # now we check whether our ancestors have metaclass, and if so borrow that
178 my ( undef, @isa ) = @{ $class->mro::get_linear_isa };
180 foreach my $ancestor ( @isa ) {
181 my $ancestor_meta = Class::MOP::get_metaclass_by_name($ancestor) || next;
183 my $ancestor_meta_class = ($ancestor_meta->is_immutable
184 ? $ancestor_meta->get_mutable_metaclass_name
185 : ref($ancestor_meta));
187 # if we have an ancestor metaclass that inherits $metaclass, we use
188 # that. This is like _fix_metaclass_incompatability, but we can do it now.
190 # the case of having an ancestry is not very common, but arises in
192 unless ( $metaclass->isa( $ancestor_meta_class ) ) {
193 if ( $ancestor_meta_class->isa($metaclass) ) {
194 $metaclass = $ancestor_meta_class;
199 $meta = $metaclass->initialize($class);
202 if ( $class->can('meta') ) {
203 # check 'meta' method
205 # it may be inherited
208 # this is the case where the metaclass pragma
209 # was used before the 'use Moose' statement to
210 # override a specific class
211 my $method_meta = $class->meta;
213 ( blessed($method_meta) && $method_meta->isa('Moose::Meta::Class') )
214 || throw_error "$class already has a &meta function, but it does not return a Moose::Meta::Class ($meta)";
216 $meta = $method_meta;
219 unless ( $meta->has_method("meta") ) { # don't overwrite
220 # also check for inherited non moose 'meta' method?
221 # FIXME also skip this if the user requested by passing an option
224 # re-initialize so it inherits properly
225 $metaclass->initialize( ref($_[0]) || $_[0] );
230 # make sure they inherit from Moose::Object
231 $meta->superclasses($base_class)
232 unless $meta->superclasses();
237 # This may be used in some older MooseX extensions.
239 goto &Moose::Exporter::_get_caller;
242 ## make 'em all immutable
244 $_->meta->make_immutable(
245 inline_constructor => 1,
246 constructor_name => "_new",
247 inline_accessors => 1, # these are Class::MOP accessors, so they need inlining
250 Moose::Meta::Attribute
252 Moose::Meta::Instance
254 Moose::Meta::TypeConstraint
255 Moose::Meta::TypeConstraint::Union
256 Moose::Meta::TypeConstraint::Parameterized
257 Moose::Meta::TypeConstraint::Parameterizable
258 Moose::Meta::TypeConstraint::Enum
259 Moose::Meta::TypeConstraint::Class
260 Moose::Meta::TypeConstraint::Role
261 Moose::Meta::TypeConstraint::Registry
262 Moose::Meta::TypeCoercion
263 Moose::Meta::TypeCoercion::Union
266 Moose::Meta::Method::Accessor
267 Moose::Meta::Method::Constructor
268 Moose::Meta::Method::Destructor
269 Moose::Meta::Method::Overriden
270 Moose::Meta::Method::Augmented
273 Moose::Meta::Role::Method
274 Moose::Meta::Role::Method::Required
276 Moose::Meta::Role::Composite
278 Moose::Meta::Role::Application
279 Moose::Meta::Role::Application::RoleSummation
280 Moose::Meta::Role::Application::ToClass
281 Moose::Meta::Role::Application::ToRole
282 Moose::Meta::Role::Application::ToInstance
293 Moose - A postmodern object system for Perl 5
298 use Moose; # automatically turns on strict and warnings
300 has 'x' => (is => 'rw', isa => 'Int');
301 has 'y' => (is => 'rw', isa => 'Int');
314 has 'z' => (is => 'rw', isa => 'Int');
316 after 'clear' => sub {
323 Moose is an extension of the Perl 5 object system.
325 The main goal of Moose is to make Perl 5 Object Oriented programming
326 easier, more consistent and less tedious. With Moose you can to think
327 more about what you want to do and less about the mechanics of OOP.
329 Additionally, Moose is built on top of L<Class::MOP>, which is a
330 metaclass system for Perl 5. This means that Moose not only makes
331 building normal Perl 5 objects better, but it provides the power of
332 metaclass programming as well.
336 If you're new to Moose, the best place to start is the L<Moose::Intro>
337 docs, followed by the L<Moose::Cookbook>. The intro will show you what
338 Moose is, and how it makes Perl 5 OO better.
340 The cookbook recipes on Moose basics will get you up to speed with
341 many of Moose's features quickly. Once you have an idea of what Moose
342 can do, you can use the API documentation to get more detail on
343 features which interest you.
345 =head2 Moose Extensions
347 The C<MooseX::> namespace is the official place to find Moose extensions.
348 These extensions can be found on the CPAN. The easiest way to find them
349 is to search for them (L<http://search.cpan.org/search?query=MooseX::>),
350 or to examine L<Task::Moose> which aims to keep an up-to-date, easily
351 installable list of Moose extensions.
353 =head1 BUILDING CLASSES WITH MOOSE
355 Moose makes every attempt to provide as much convenience as possible during
356 class construction/definition, but still stay out of your way if you want it
357 to. Here are a few items to note when building classes with Moose.
359 Unless specified with C<extends>, any class which uses Moose will
360 inherit from L<Moose::Object>.
362 Moose will also manage all attributes (including inherited ones) that are
363 defined with C<has>. And (assuming you call C<new>, which is inherited from
364 L<Moose::Object>) this includes properly initializing all instance slots,
365 setting defaults where appropriate, and performing any type constraint checking
368 =head1 PROVIDED METHODS
370 Moose provides a number of methods to all your classes, mostly through the
371 inheritance of L<Moose::Object>. There is however, one exception.
377 This is a method which provides access to the current class's metaclass.
381 =head1 EXPORTED FUNCTIONS
383 Moose will export a number of functions into the class's namespace which
384 may then be used to set up the class. These functions all work directly
385 on the current class.
389 =item B<extends (@superclasses)>
391 This function will set the superclass(es) for the current class.
393 This approach is recommended instead of C<use base>, because C<use base>
394 actually C<push>es onto the class's C<@ISA>, whereas C<extends> will
395 replace it. This is important to ensure that classes which do not have
396 superclasses still properly inherit from L<Moose::Object>.
398 =item B<with (@roles)>
400 This will apply a given set of C<@roles> to the local class.
402 =item B<has $name =E<gt> %options>
404 This will install an attribute of a given C<$name> into the current class.
405 The C<%options> are the same as those provided by
406 L<Class::MOP::Attribute>, in addition to the list below which are provided
407 by Moose (L<Moose::Meta::Attribute> to be more specific):
411 =item I<is =E<gt> 'rw'|'ro'>
413 The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read
414 only). These will create either a read/write accessor or a read-only
415 accessor respectively, using the same name as the C<$name> of the attribute.
417 If you need more control over how your accessors are named, you can use the
418 I<reader>, I<writer> and I<accessor> options inherited from
419 L<Class::MOP::Attribute>, however if you use those, you won't need the I<is>
422 =item I<isa =E<gt> $type_name>
424 The I<isa> option uses Moose's type constraint facilities to set up runtime
425 type checking for this attribute. Moose will perform the checks during class
426 construction, and within any accessors. The C<$type_name> argument must be a
427 string. The string may be either a class name or a type defined using
428 Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
429 for information on how to define a new type, and how to retrieve type meta-data).
431 =item I<coerce =E<gt> (1|0)>
433 This will attempt to use coercion with the supplied type constraint to change
434 the value passed into any accessors or constructors. You B<must> have supplied
435 a type constraint in order for this to work. See L<Moose::Cookbook::Basics::Recipe5>
438 =item I<does =E<gt> $role_name>
440 This will accept the name of a role which the value stored in this attribute
441 is expected to have consumed.
443 =item I<required =E<gt> (1|0)>
445 This marks the attribute as being required. This means a I<defined> value must be
446 supplied during class construction, and the attribute may never be set to
447 C<undef> with an accessor.
449 =item I<weak_ref =E<gt> (1|0)>
451 This will tell the class to store the value of this attribute as a weakened
452 reference. If an attribute is a weakened reference, it B<cannot> also be
455 =item I<lazy =E<gt> (1|0)>
457 This will tell the class to not create this slot until absolutely necessary.
458 If an attribute is marked as lazy it B<must> have a default supplied.
460 =item I<auto_deref =E<gt> (1|0)>
462 This tells the accessor whether to automatically dereference the value returned.
463 This is only legal if your C<isa> option is either C<ArrayRef> or C<HashRef>.
465 =item I<trigger =E<gt> $code>
467 The I<trigger> option is a CODE reference which will be called after the value of
468 the attribute is set. The CODE ref will be passed the instance itself, the
469 updated value and the attribute meta-object (this is for more advanced fiddling
470 and can typically be ignored). You B<cannot> have a trigger on a read-only
473 =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
475 The I<handles> option provides Moose classes with automated delegation features.
476 This is a pretty complex and powerful option. It accepts many different option
477 formats, each with its own benefits and drawbacks.
479 B<NOTE:> The class being delegated to does not need to be a Moose based class,
480 which is why this feature is especially useful when wrapping non-Moose classes.
482 All I<handles> option formats share the following traits:
484 You cannot override a locally defined method with a delegated method; an
485 exception will be thrown if you try. That is to say, if you define C<foo> in
486 your class, you cannot override it with a delegated C<foo>. This is almost never
487 something you would want to do, and if it is, you should do it by hand and not
490 You cannot override any of the methods found in Moose::Object, or the C<BUILD>
491 and C<DEMOLISH> methods. These will not throw an exception, but will silently
492 move on to the next method in the list. My reasoning for this is that you would
493 almost never want to do this, since it usually breaks your class. As with
494 overriding locally defined methods, if you do want to do this, you should do it
495 manually, not with Moose.
497 You do not I<need> to have a reader (or accessor) for the attribute in order
498 to delegate to it. Moose will create a means of accessing the value for you,
499 however this will be several times B<less> efficient then if you had given
500 the attribute a reader (or accessor) to use.
502 Below is the documentation for each option format:
508 This is the most common usage for I<handles>. You basically pass a list of
509 method names to be delegated, and Moose will install a delegation method
514 This is the second most common usage for I<handles>. Instead of a list of
515 method names, you pass a HASH ref where each key is the method name you
516 want installed locally, and its value is the name of the original method
517 in the class being delegated to.
519 This can be very useful for recursive classes like trees. Here is a
520 quick example (soon to be expanded into a Moose::Cookbook recipe):
525 has 'node' => (is => 'rw', isa => 'Any');
530 default => sub { [] }
538 parent_node => 'node',
539 siblings => 'children',
543 In this example, the Tree package gets C<parent_node> and C<siblings> methods,
544 which delegate to the C<node> and C<children> methods (respectively) of the Tree
545 instance stored in the C<parent> slot.
549 The regexp option works very similar to the ARRAY option, except that it builds
550 the list of methods for you. It starts by collecting all possible methods of the
551 class being delegated to, then filters that list using the regexp supplied here.
553 B<NOTE:> An I<isa> option is required when using the regexp option format. This
554 is so that we can determine (at compile time) the method list from the class.
555 Without an I<isa> this is just not possible.
559 With the role option, you specify the name of a role whose "interface" then
560 becomes the list of methods to handle. The "interface" can be defined as; the
561 methods of the role and any required methods of the role. It should be noted
562 that this does B<not> include any method modifiers or generated attribute
563 methods (which is consistent with role composition).
567 This is the option to use when you really want to do something funky. You should
568 only use it if you really know what you are doing, as it involves manual
571 This takes a code reference, which should expect two arguments. The first is the
572 attribute meta-object this I<handles> is attached to. The second is the
573 metaclass of the class being delegated to. It expects you to return a hash (not
574 a HASH ref) of the methods you want mapped.
578 =item I<metaclass =E<gt> $metaclass_name>
580 This tells the class to use a custom attribute metaclass for this particular
581 attribute. Custom attribute metaclasses are useful for extending the
582 capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
583 but they are still a fairly advanced topic and too much to cover here, see
584 L<Moose::Cookbook::Meta::Recipe1> for more information.
586 The default behavior here is to just load C<$metaclass_name>; however, we also
587 have a way to alias to a shorter name. This will first look to see if
588 B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose
589 will then check to see if that has the method C<register_implementation>, which
590 should return the actual name of the custom attribute metaclass. If there is no
591 C<register_implementation> method, it will fall back to using
592 B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name.
594 =item I<traits =E<gt> [ @role_names ]>
596 This tells Moose to take the list of C<@role_names> and apply them to the
597 attribute meta-object. This is very similar to the I<metaclass> option, but
598 allows you to use more than one extension at a time.
600 See L<TRAIT NAME RESOLUTION> for details on how a trait name is
601 resolved to a class name.
603 Also see L<Moose::Cookbook::Meta::Recipe3> for a metaclass trait
608 =item B<has +$name =E<gt> %options>
610 This is variation on the normal attibute creator C<has> which allows you to
611 clone and extend an attribute from a superclass or from a role. Here is an
612 example of the superclass usage:
620 default => 'Hello, I am a Foo'
628 has '+message' => (default => 'Hello I am My::Foo');
630 What is happening here is that B<My::Foo> is cloning the C<message> attribute
631 from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt>
632 'Str'> characteristics, but changing the value in C<default>.
634 Here is another example, but within the context of a role:
642 default => 'Hello, I am a Foo'
650 has '+message' => (default => 'Hello I am My::Foo');
652 In this case, we are basically taking the attribute which the role supplied
653 and altering it within the bounds of this feature.
655 Aside from where the attributes come from (one from superclass, the other
656 from a role), this feature works exactly the same. This feature is restricted
657 somewhat, so as to try and force at least I<some> sanity into it. You are only
658 allowed to change the following attributes:
664 Change the default value of an attribute.
668 Change whether the attribute attempts to coerce a value passed to it.
672 Change if the attribute is required to have a value.
674 =item I<documentation>
676 Change the documentation string associated with the attribute.
680 Change if the attribute lazily initializes the slot.
684 You I<are> allowed to change the type without restriction.
686 It is recommended that you use this freedom with caution. We used to
687 only allow for extension only if the type was a subtype of the parent's
688 type, but we felt that was too restrictive and is better left as a
693 You are allowed to B<add> a new C<handles> definition, but you are B<not>
694 allowed to I<change> one.
698 You are allowed to B<add> a new C<builder> definition, but you are B<not>
699 allowed to I<change> one.
703 You are allowed to B<add> a new C<metaclass> definition, but you are
704 B<not> allowed to I<change> one.
708 You are allowed to B<add> additional traits to the C<traits> definition.
709 These traits will be composed into the attribute, but pre-existing traits
710 B<are not> overridden, or removed.
714 =item B<before $name|@names =E<gt> sub { ... }>
716 =item B<after $name|@names =E<gt> sub { ... }>
718 =item B<around $name|@names =E<gt> sub { ... }>
720 This three items are syntactic sugar for the before, after, and around method
721 modifier features that L<Class::MOP> provides. More information on these may be
722 found in the L<Class::MOP::Class documentation|Class::MOP::Class/"Method
727 The keyword C<super> is a no-op when called outside of an C<override> method. In
728 the context of an C<override> method, it will call the next most appropriate
729 superclass method with the same arguments as the original method.
731 =item B<override ($name, &sub)>
733 An C<override> method is a way of explicitly saying "I am overriding this
734 method from my superclass". You can call C<super> within this method, and
735 it will work as expected. The same thing I<can> be accomplished with a normal
736 method call and the C<SUPER::> pseudo-package; it is really your choice.
740 The keyword C<inner>, much like C<super>, is a no-op outside of the context of
741 an C<augment> method. You can think of C<inner> as being the inverse of
742 C<super>; the details of how C<inner> and C<augment> work is best described in
743 the L<Moose::Cookbook::Basics::Recipe6>.
745 =item B<augment ($name, &sub)>
747 An C<augment> method, is a way of explicitly saying "I am augmenting this
748 method from my superclass". Once again, the details of how C<inner> and
749 C<augment> work is best described in the L<Moose::Cookbook::Basics::Recipe6>.
753 This is the C<Carp::confess> function, and exported here because I use it
758 This is the C<Scalar::Util::blessed> function, it is exported here because I
759 use it all the time. It is highly recommended that this is used instead of
760 C<ref> anywhere you need to test for an object's class name.
764 =head1 METACLASS TRAITS
766 When you use Moose, you can also specify traits which will be applied
769 use Moose -traits => 'My::Trait';
771 This is very similar to the attribute traits feature. When you do
772 this, your class's C<meta> object will have the specified traits
773 applied to it. See L<TRAIT NAME RESOLUTION> for more details.
775 =head1 TRAIT NAME RESOLUTION
777 By default, when given a trait name, Moose simply tries to load a
778 class of the same name. If such a class does not exist, it then looks
779 for for a class matching
780 B<Moose::Meta::$type::Custom::Trait::$trait_name>. The C<$type>
781 variable here will be one of B<Attribute> or B<Class>, depending on
782 what the trait is being applied to.
784 If a class with this long name exists, Moose checks to see if it has
785 the method C<register_implementation>. This method is expected to
786 return the I<real> class name of the trait. If there is no
787 C<register_implementation> method, it will fall back to using
788 B<Moose::Meta::$type::Custom::Trait::$trait> as the trait name.
790 If all this is confusing, take a look at
791 L<Moose::Cookbook::Meta::Recipe3>, which demonstrates how to create an
794 =head1 UNIMPORTING FUNCTIONS
798 Moose offers a way to remove the keywords it exports, through the C<unimport>
799 method. You simply have to say C<no Moose> at the bottom of your code for this
800 to work. Here is an example:
805 has 'first_name' => (is => 'rw', isa => 'Str');
806 has 'last_name' => (is => 'rw', isa => 'Str');
810 $self->first_name . ' ' . $self->last_name
813 no Moose; # keywords are removed from the Person package
815 =head1 EXTENDING AND EMBEDDING MOOSE
817 Moose also offers some options for extending or embedding it into your
818 own framework. To learn more about extending Moose, we recommend
819 checking out the "Extending" recipes in the L<Moose::Cookbook>,
820 starting with L<Moose::Cookbook::Extending::Recipe1>, which provides
821 an overview of all the different ways you might extend Moose.
823 =head2 B<< Moose->init_meta(for_class => $class, base_class => $baseclass, metaclass => $metaclass) >>
825 The C<init_meta> method sets up the metaclass object for the class
826 specified by C<for_class>. This method injects a a C<meta> accessor
827 into the class so you can get at this object. It also sets the class's
828 superclass to C<base_class>, with L<Moose::Object> as the default.
830 You can specify an alternate metaclass with the C<metaclass> parameter.
832 For more detail on this topic, see L<Moose::Cookbook::Extending::Recipe2>.
834 This method used to be documented as a function which accepted
835 positional parameters. This calling style will still work for
836 backwards compatibility, but is deprecated.
840 Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
841 and C<{into_level =E<gt> 1}>.
843 B<NOTE>: Doing this is more or less deprecated. Use L<Moose::Exporter>
844 instead, which lets you stack multiple C<Moose.pm>-alike modules
845 sanely. It handles getting the exported functions into the right place
850 An alias for C<confess>, used by internally by Moose.
858 It should be noted that C<super> and C<inner> B<cannot> be used in the same
859 method. However, they may be combined within the same class hierarchy; see
860 F<t/014_override_augment_inner_super.t> for an example.
862 The reason for this is that C<super> is only valid within a method
863 with the C<override> modifier, and C<inner> will never be valid within an
864 C<override> method. In fact, C<augment> will skip over any C<override> methods
865 when searching for its appropriate C<inner>.
867 This might seem like a restriction, but I am of the opinion that keeping these
868 two features separate (yet interoperable) actually makes them easy to use, since
869 their behavior is then easier to predict. Time will tell whether I am right or
870 not (UPDATE: so far so good).
874 =head1 ACKNOWLEDGEMENTS
878 =item I blame Sam Vilain for introducing me to the insanity that is meta-models.
880 =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6.
882 =item Without Yuval "nothingmuch" Kogman this module would not be possible,
883 and it certainly wouldn't have this name ;P
885 =item The basis of the TypeContraints module was Rob Kinyon's idea
886 originally, I just ran with it.
888 =item Thanks to mst & chansen and the whole #moose posse for all the
889 early ideas/feature-requests/encouragement/bug-finding.
891 =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes.
899 =item L<http://www.iinteractive.com/moose>
901 This is the official web home of Moose, it contains links to our public SVN repo
902 as well as links to a number of talks and articles on Moose and Moose related
905 =item L<Moose::Cookbook> - How to cook a Moose
907 =item The Moose is flying, a tutorial by Randal Schwartz
909 Part 1 - L<http://www.stonehenge.com/merlyn/LinuxMag/col94.html>
911 Part 2 - L<http://www.stonehenge.com/merlyn/LinuxMag/col95.html>
913 =item L<Class::MOP> documentation
915 =item The #moose channel on irc.perl.org
917 =item The Moose mailing list - moose@perl.org
919 =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/moose>
921 =item Several Moose extension modules in the C<MooseX::> namespace.
923 See L<http://search.cpan.org/search?query=MooseX::> for extensions.
931 =item The Art of the MetaObject Protocol
933 I mention this in the L<Class::MOP> docs too, this book was critical in
934 the development of both modules and is highly recommended.
942 =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf>
944 This paper (suggested by lbr on #moose) was what lead to the implementation
945 of the C<super>/C<override> and C<inner>/C<augment> features. If you really
946 want to understand them, I suggest you read this.
952 All complex software has bugs lurking in it, and this module is no
953 exception. If you find a bug please either email me, or add the bug
956 =head1 FEATURE REQUESTS
958 We are very strict about what features we add to the Moose core, especially
959 the user-visible features. Instead we have made sure that the underlying
960 meta-system of Moose is as extensible as possible so that you can add your
961 own features easily. That said, occasionally there is a feature needed in the
962 meta-system to support your planned extension, in which case you should
963 either email the mailing list or join us on irc at #moose to discuss.
967 Stevan Little E<lt>stevan@iinteractive.comE<gt>
969 B<with contributions from:>
975 Anders (Debolaz) Nor Berle
977 Nathan (kolibre) Gray
979 Christian (chansen) Hansen
981 Hans Dieter (confound) Pearcey
983 Eric (ewilhelm) Wilhelm
985 Guillermo (groditi) Roditi
987 Jess (castaway) Robinson
991 Robert (phaylon) Sedlacek
995 Scott (konobi) McWhirter
997 Shlomi (rindolf) Fish
999 Yuval (nothingmuch) Kogman
1001 Chris (perigrin) Prather
1003 Wallace (wreis) Reis
1005 Jonathan (jrockway) Rockway
1007 Dave (autarch) Rolsky
1009 Piotr (dexter) Roszatycki
1011 Sam (mugwump) Vilain
1013 Shawn (sartak) Moore
1015 ... and many other #moose folks
1017 =head1 COPYRIGHT AND LICENSE
1019 Copyright 2006-2008 by Infinity Interactive, Inc.
1021 L<http://www.iinteractive.com>
1023 This library is free software; you can redistribute it and/or modify
1024 it under the same terms as Perl itself.