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;
48 croak "Must derive at least one class" unless @_;
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')
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
64 my $meta = Moose::Meta::Class->initialize($class);
65 $meta->_fix_metaclass_incompatibility(@supers);
66 $meta->superclasses(@supers);
71 Moose::Util::apply_all_roles(Class::MOP::Class->initialize($class), @_);
77 croak 'Usage: has \'name\' => ( key => value, ... )' if @_ == 1;
79 my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ];
80 Class::MOP::Class->initialize($class)->add_attribute( $_, %options ) for @$attrs;
85 Moose::Util::add_method_modifier($class, 'before', \@_);
90 Moose::Util::add_method_modifier($class, 'after', \@_);
95 Moose::Util::add_method_modifier($class, 'around', \@_);
99 return unless our $SUPER_BODY; $SUPER_BODY->(our @SUPER_ARGS);
104 my ( $name, $method ) = @_;
105 Class::MOP::Class->initialize($class)->add_override_method_modifier( $name => $method );
110 our ( %INNER_BODY, %INNER_ARGS );
112 if ( my $body = $INNER_BODY{$pkg} ) {
113 my @args = @{ $INNER_ARGS{$pkg} };
114 local $INNER_ARGS{$pkg};
115 local $INNER_BODY{$pkg};
116 return $body->(@args);
124 my ( $name, $method ) = @_;
125 Class::MOP::Class->initialize($class)->add_augment_method_modifier( $name => $method );
130 cluck "The make_immutable keyword has been deprecated, " .
131 "please go back to __PACKAGE__->meta->make_immutable\n";
132 Class::MOP::Class->initialize($class)->make_immutable(@_);
135 Moose::Exporter->setup_import_methods(
137 qw( extends with has before after around override augment make_immutable )
142 \&Scalar::Util::blessed,
147 # This used to be called as a function. This hack preserves
148 # backwards compatibility.
149 if ( $_[0] ne __PACKAGE__ ) {
150 return __PACKAGE__->init_meta(
160 my $class = $args{for_class}
161 or Moose->throw_error("Cannot call init_meta without specifying a for_class");
162 my $base_class = $args{base_class} || 'Moose::Object';
163 my $metaclass = $args{metaclass} || 'Moose::Meta::Class';
165 Moose->throw_error("The Metaclass $metaclass must be a subclass of Moose::Meta::Class.")
166 unless $metaclass->isa('Moose::Meta::Class');
168 # make a subtype for each Moose class
170 unless find_type_constraint($class);
174 if ( $meta = Class::MOP::get_metaclass_by_name($class) ) {
175 unless ( $meta->isa("Moose::Meta::Class") ) {
176 Moose->throw_error("$class already has a metaclass, but it does not inherit $metaclass ($meta)");
179 # no metaclass, no 'meta' method
181 # now we check whether our ancestors have metaclass, and if so borrow that
182 my ( undef, @isa ) = @{ $class->mro::get_linear_isa };
184 foreach my $ancestor ( @isa ) {
185 my $ancestor_meta = Class::MOP::get_metaclass_by_name($ancestor) || next;
187 my $ancestor_meta_class = ($ancestor_meta->is_immutable
188 ? $ancestor_meta->get_mutable_metaclass_name
189 : ref($ancestor_meta));
191 # if we have an ancestor metaclass that inherits $metaclass, we use
192 # that. This is like _fix_metaclass_incompatibility, but we can do it now.
194 # the case of having an ancestry is not very common, but arises in
196 unless ( $metaclass->isa( $ancestor_meta_class ) ) {
197 if ( $ancestor_meta_class->isa($metaclass) ) {
198 $metaclass = $ancestor_meta_class;
203 $meta = $metaclass->initialize($class);
206 if ( $class->can('meta') ) {
207 # check 'meta' method
209 # it may be inherited
212 # this is the case where the metaclass pragma
213 # was used before the 'use Moose' statement to
214 # override a specific class
215 my $method_meta = $class->meta;
217 ( blessed($method_meta) && $method_meta->isa('Moose::Meta::Class') )
218 || Moose->throw_error("$class already has a &meta function, but it does not return a Moose::Meta::Class ($meta)");
220 $meta = $method_meta;
223 unless ( $meta->has_method("meta") ) { # don't overwrite
224 # also check for inherited non moose 'meta' method?
225 # FIXME also skip this if the user requested by passing an option
228 # re-initialize so it inherits properly
229 $metaclass->initialize( ref($_[0]) || $_[0] );
234 # make sure they inherit from Moose::Object
235 $meta->superclasses($base_class)
236 unless $meta->superclasses();
241 # This may be used in some older MooseX extensions.
243 goto &Moose::Exporter::_get_caller;
246 ## make 'em all immutable
248 $_->meta->make_immutable(
249 inline_constructor => 1,
250 constructor_name => "_new",
251 inline_accessors => 1, # these are Class::MOP accessors, so they need inlining
254 Moose::Meta::Attribute
256 Moose::Meta::Instance
258 Moose::Meta::TypeConstraint
259 Moose::Meta::TypeConstraint::Union
260 Moose::Meta::TypeConstraint::Parameterized
261 Moose::Meta::TypeConstraint::Parameterizable
262 Moose::Meta::TypeConstraint::Enum
263 Moose::Meta::TypeConstraint::Class
264 Moose::Meta::TypeConstraint::Role
265 Moose::Meta::TypeConstraint::Registry
266 Moose::Meta::TypeCoercion
267 Moose::Meta::TypeCoercion::Union
270 Moose::Meta::Method::Accessor
271 Moose::Meta::Method::Constructor
272 Moose::Meta::Method::Destructor
273 Moose::Meta::Method::Overriden
274 Moose::Meta::Method::Augmented
277 Moose::Meta::Role::Method
278 Moose::Meta::Role::Method::Required
280 Moose::Meta::Role::Composite
282 Moose::Meta::Role::Application
283 Moose::Meta::Role::Application::RoleSummation
284 Moose::Meta::Role::Application::ToClass
285 Moose::Meta::Role::Application::ToRole
286 Moose::Meta::Role::Application::ToInstance
297 Moose - A postmodern object system for Perl 5
302 use Moose; # automatically turns on strict and warnings
304 has 'x' => (is => 'rw', isa => 'Int');
305 has 'y' => (is => 'rw', isa => 'Int');
318 has 'z' => (is => 'rw', isa => 'Int');
320 after 'clear' => sub {
327 Moose is an extension of the Perl 5 object system.
329 The main goal of Moose is to make Perl 5 Object Oriented programming
330 easier, more consistent and less tedious. With Moose you can to think
331 more about what you want to do and less about the mechanics of OOP.
333 Additionally, Moose is built on top of L<Class::MOP>, which is a
334 metaclass system for Perl 5. This means that Moose not only makes
335 building normal Perl 5 objects better, but it provides the power of
336 metaclass programming as well.
340 If you're new to Moose, the best place to start is the L<Moose::Intro>
341 docs, followed by the L<Moose::Cookbook>. The intro will show you what
342 Moose is, and how it makes Perl 5 OO better.
344 The cookbook recipes on Moose basics will get you up to speed with
345 many of Moose's features quickly. Once you have an idea of what Moose
346 can do, you can use the API documentation to get more detail on
347 features which interest you.
349 =head2 Moose Extensions
351 The C<MooseX::> namespace is the official place to find Moose extensions.
352 These extensions can be found on the CPAN. The easiest way to find them
353 is to search for them (L<http://search.cpan.org/search?query=MooseX::>),
354 or to examine L<Task::Moose> which aims to keep an up-to-date, easily
355 installable list of Moose extensions.
357 =head1 BUILDING CLASSES WITH MOOSE
359 Moose makes every attempt to provide as much convenience as possible during
360 class construction/definition, but still stay out of your way if you want it
361 to. Here are a few items to note when building classes with Moose.
363 Unless specified with C<extends>, any class which uses Moose will
364 inherit from L<Moose::Object>.
366 Moose will also manage all attributes (including inherited ones) that are
367 defined with C<has>. And (assuming you call C<new>, which is inherited from
368 L<Moose::Object>) this includes properly initializing all instance slots,
369 setting defaults where appropriate, and performing any type constraint checking
372 =head1 PROVIDED METHODS
374 Moose provides a number of methods to all your classes, mostly through the
375 inheritance of L<Moose::Object>. There is however, one exception.
381 This is a method which provides access to the current class's metaclass.
385 =head1 EXPORTED FUNCTIONS
387 Moose will export a number of functions into the class's namespace which
388 may then be used to set up the class. These functions all work directly
389 on the current class.
393 =item B<extends (@superclasses)>
395 This function will set the superclass(es) for the current class.
397 This approach is recommended instead of C<use base>, because C<use base>
398 actually C<push>es onto the class's C<@ISA>, whereas C<extends> will
399 replace it. This is important to ensure that classes which do not have
400 superclasses still properly inherit from L<Moose::Object>.
402 =item B<with (@roles)>
404 This will apply a given set of C<@roles> to the local class.
406 =item B<has $name =E<gt> %options>
408 This will install an attribute of a given C<$name> into the current class.
409 The C<%options> are the same as those provided by
410 L<Class::MOP::Attribute>, in addition to the list below which are provided
411 by Moose (L<Moose::Meta::Attribute> to be more specific):
415 =item I<is =E<gt> 'rw'|'ro'>
417 The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read
418 only). These will create either a read/write accessor or a read-only
419 accessor respectively, using the same name as the C<$name> of the attribute.
421 If you need more control over how your accessors are named, you can use the
422 I<reader>, I<writer> and I<accessor> options inherited from
423 L<Class::MOP::Attribute>, however if you use those, you won't need the I<is>
426 =item I<isa =E<gt> $type_name>
428 The I<isa> option uses Moose's type constraint facilities to set up runtime
429 type checking for this attribute. Moose will perform the checks during class
430 construction, and within any accessors. The C<$type_name> argument must be a
431 string. The string may be either a class name or a type defined using
432 Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
433 for information on how to define a new type, and how to retrieve type meta-data).
435 =item I<coerce =E<gt> (1|0)>
437 This will attempt to use coercion with the supplied type constraint to change
438 the value passed into any accessors or constructors. You B<must> have supplied
439 a type constraint in order for this to work. See L<Moose::Cookbook::Basics::Recipe5>
442 =item I<does =E<gt> $role_name>
444 This will accept the name of a role which the value stored in this attribute
445 is expected to have consumed.
447 =item I<required =E<gt> (1|0)>
449 This marks the attribute as being required. This means a I<defined> value must be
450 supplied during class construction, and the attribute may never be set to
451 C<undef> with an accessor.
453 =item I<weak_ref =E<gt> (1|0)>
455 This will tell the class to store the value of this attribute as a weakened
456 reference. If an attribute is a weakened reference, it B<cannot> also be
459 =item I<lazy =E<gt> (1|0)>
461 This will tell the class to not create this slot until absolutely necessary.
462 If an attribute is marked as lazy it B<must> have a default supplied.
464 =item I<auto_deref =E<gt> (1|0)>
466 This tells the accessor whether to automatically dereference the value returned.
467 This is only legal if your C<isa> option is either C<ArrayRef> or C<HashRef>.
469 =item I<trigger =E<gt> $code>
471 The I<trigger> option is a CODE reference which will be called after the value of
472 the attribute is set. The CODE ref will be passed the instance itself, the
473 updated value and the attribute meta-object (this is for more advanced fiddling
474 and can typically be ignored). You B<cannot> have a trigger on a read-only
477 =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
479 The I<handles> option provides Moose classes with automated delegation features.
480 This is a pretty complex and powerful option. It accepts many different option
481 formats, each with its own benefits and drawbacks.
483 B<NOTE:> The class being delegated to does not need to be a Moose based class,
484 which is why this feature is especially useful when wrapping non-Moose classes.
486 All I<handles> option formats share the following traits:
488 You cannot override a locally defined method with a delegated method; an
489 exception will be thrown if you try. That is to say, if you define C<foo> in
490 your class, you cannot override it with a delegated C<foo>. This is almost never
491 something you would want to do, and if it is, you should do it by hand and not
494 You cannot override any of the methods found in Moose::Object, or the C<BUILD>
495 and C<DEMOLISH> methods. These will not throw an exception, but will silently
496 move on to the next method in the list. My reasoning for this is that you would
497 almost never want to do this, since it usually breaks your class. As with
498 overriding locally defined methods, if you do want to do this, you should do it
499 manually, not with Moose.
501 You do not I<need> to have a reader (or accessor) for the attribute in order
502 to delegate to it. Moose will create a means of accessing the value for you,
503 however this will be several times B<less> efficient then if you had given
504 the attribute a reader (or accessor) to use.
506 Below is the documentation for each option format:
512 This is the most common usage for I<handles>. You basically pass a list of
513 method names to be delegated, and Moose will install a delegation method
518 This is the second most common usage for I<handles>. Instead of a list of
519 method names, you pass a HASH ref where each key is the method name you
520 want installed locally, and its value is the name of the original method
521 in the class being delegated to.
523 This can be very useful for recursive classes like trees. Here is a
524 quick example (soon to be expanded into a Moose::Cookbook recipe):
529 has 'node' => (is => 'rw', isa => 'Any');
534 default => sub { [] }
542 parent_node => 'node',
543 siblings => 'children',
547 In this example, the Tree package gets C<parent_node> and C<siblings> methods,
548 which delegate to the C<node> and C<children> methods (respectively) of the Tree
549 instance stored in the C<parent> slot.
553 The regexp option works very similar to the ARRAY option, except that it builds
554 the list of methods for you. It starts by collecting all possible methods of the
555 class being delegated to, then filters that list using the regexp supplied here.
557 B<NOTE:> An I<isa> option is required when using the regexp option format. This
558 is so that we can determine (at compile time) the method list from the class.
559 Without an I<isa> this is just not possible.
563 With the role option, you specify the name of a role whose "interface" then
564 becomes the list of methods to handle. The "interface" can be defined as; the
565 methods of the role and any required methods of the role. It should be noted
566 that this does B<not> include any method modifiers or generated attribute
567 methods (which is consistent with role composition).
571 This is the option to use when you really want to do something funky. You should
572 only use it if you really know what you are doing, as it involves manual
575 This takes a code reference, which should expect two arguments. The first is the
576 attribute meta-object this I<handles> is attached to. The second is the
577 metaclass of the class being delegated to. It expects you to return a hash (not
578 a HASH ref) of the methods you want mapped.
582 =item I<metaclass =E<gt> $metaclass_name>
584 This tells the class to use a custom attribute metaclass for this particular
585 attribute. Custom attribute metaclasses are useful for extending the
586 capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
587 but they are still a fairly advanced topic and too much to cover here, see
588 L<Moose::Cookbook::Meta::Recipe1> for more information.
590 The default behavior here is to just load C<$metaclass_name>; however, we also
591 have a way to alias to a shorter name. This will first look to see if
592 B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose
593 will then check to see if that has the method C<register_implementation>, which
594 should return the actual name of the custom attribute metaclass. If there is no
595 C<register_implementation> method, it will fall back to using
596 B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name.
598 =item I<traits =E<gt> [ @role_names ]>
600 This tells Moose to take the list of C<@role_names> and apply them to the
601 attribute meta-object. This is very similar to the I<metaclass> option, but
602 allows you to use more than one extension at a time.
604 See L<TRAIT NAME RESOLUTION> for details on how a trait name is
605 resolved to a class name.
607 Also see L<Moose::Cookbook::Meta::Recipe3> for a metaclass trait
612 =item B<has +$name =E<gt> %options>
614 This is variation on the normal attibute creator C<has> which allows you to
615 clone and extend an attribute from a superclass or from a role. Here is an
616 example of the superclass usage:
624 default => 'Hello, I am a Foo'
632 has '+message' => (default => 'Hello I am My::Foo');
634 What is happening here is that B<My::Foo> is cloning the C<message> attribute
635 from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt>
636 'Str'> characteristics, but changing the value in C<default>.
638 Here is another example, but within the context of a role:
646 default => 'Hello, I am a Foo'
654 has '+message' => (default => 'Hello I am My::Foo');
656 In this case, we are basically taking the attribute which the role supplied
657 and altering it within the bounds of this feature.
659 Aside from where the attributes come from (one from superclass, the other
660 from a role), this feature works exactly the same. This feature is restricted
661 somewhat, so as to try and force at least I<some> sanity into it. You are only
662 allowed to change the following attributes:
668 Change the default value of an attribute.
672 Change whether the attribute attempts to coerce a value passed to it.
676 Change if the attribute is required to have a value.
678 =item I<documentation>
680 Change the documentation string associated with the attribute.
684 Change if the attribute lazily initializes the slot.
688 You I<are> allowed to change the type without restriction.
690 It is recommended that you use this freedom with caution. We used to
691 only allow for extension only if the type was a subtype of the parent's
692 type, but we felt that was too restrictive and is better left as a
697 You are allowed to B<add> a new C<handles> definition, but you are B<not>
698 allowed to I<change> one.
702 You are allowed to B<add> a new C<builder> definition, but you are B<not>
703 allowed to I<change> one.
707 You are allowed to B<add> a new C<metaclass> definition, but you are
708 B<not> allowed to I<change> one.
712 You are allowed to B<add> additional traits to the C<traits> definition.
713 These traits will be composed into the attribute, but pre-existing traits
714 B<are not> overridden, or removed.
718 =item B<before $name|@names =E<gt> sub { ... }>
720 =item B<after $name|@names =E<gt> sub { ... }>
722 =item B<around $name|@names =E<gt> sub { ... }>
724 This three items are syntactic sugar for the before, after, and around method
725 modifier features that L<Class::MOP> provides. More information on these may be
726 found in the L<Class::MOP::Class documentation|Class::MOP::Class/"Method
731 The keyword C<super> is a no-op when called outside of an C<override> method. In
732 the context of an C<override> method, it will call the next most appropriate
733 superclass method with the same arguments as the original method.
735 =item B<override ($name, &sub)>
737 An C<override> method is a way of explicitly saying "I am overriding this
738 method from my superclass". You can call C<super> within this method, and
739 it will work as expected. The same thing I<can> be accomplished with a normal
740 method call and the C<SUPER::> pseudo-package; it is really your choice.
744 The keyword C<inner>, much like C<super>, is a no-op outside of the context of
745 an C<augment> method. You can think of C<inner> as being the inverse of
746 C<super>; the details of how C<inner> and C<augment> work is best described in
747 the L<Moose::Cookbook::Basics::Recipe6>.
749 =item B<augment ($name, &sub)>
751 An C<augment> method, is a way of explicitly saying "I am augmenting this
752 method from my superclass". Once again, the details of how C<inner> and
753 C<augment> work is best described in the L<Moose::Cookbook::Basics::Recipe6>.
757 This is the C<Carp::confess> function, and exported here because I use it
762 This is the C<Scalar::Util::blessed> function, it is exported here because I
763 use it all the time. It is highly recommended that this is used instead of
764 C<ref> anywhere you need to test for an object's class name.
768 =head1 METACLASS TRAITS
770 When you use Moose, you can also specify traits which will be applied
773 use Moose -traits => 'My::Trait';
775 This is very similar to the attribute traits feature. When you do
776 this, your class's C<meta> object will have the specified traits
777 applied to it. See L<TRAIT NAME RESOLUTION> for more details.
779 =head1 TRAIT NAME RESOLUTION
781 By default, when given a trait name, Moose simply tries to load a
782 class of the same name. If such a class does not exist, it then looks
783 for for a class matching
784 B<Moose::Meta::$type::Custom::Trait::$trait_name>. The C<$type>
785 variable here will be one of B<Attribute> or B<Class>, depending on
786 what the trait is being applied to.
788 If a class with this long name exists, Moose checks to see if it has
789 the method C<register_implementation>. This method is expected to
790 return the I<real> class name of the trait. If there is no
791 C<register_implementation> method, it will fall back to using
792 B<Moose::Meta::$type::Custom::Trait::$trait> as the trait name.
794 If all this is confusing, take a look at
795 L<Moose::Cookbook::Meta::Recipe3>, which demonstrates how to create an
798 =head1 UNIMPORTING FUNCTIONS
802 Moose offers a way to remove the keywords it exports, through the C<unimport>
803 method. You simply have to say C<no Moose> at the bottom of your code for this
804 to work. Here is an example:
809 has 'first_name' => (is => 'rw', isa => 'Str');
810 has 'last_name' => (is => 'rw', isa => 'Str');
814 $self->first_name . ' ' . $self->last_name
817 no Moose; # keywords are removed from the Person package
819 =head1 EXTENDING AND EMBEDDING MOOSE
821 To learn more about extending Moose, we recommend checking out the
822 "Extending" recipes in the L<Moose::Cookbook>, starting with
823 L<Moose::Cookbook::Extending::Recipe1>, which provides an overview of
824 all the different ways you might extend Moose.
826 =head2 B<< Moose->init_meta(for_class => $class, base_class => $baseclass, metaclass => $metaclass) >>
828 The C<init_meta> method sets up the metaclass object for the class
829 specified by C<for_class>. This method injects a a C<meta> accessor
830 into the class so you can get at this object. It also sets the class's
831 superclass to C<base_class>, with L<Moose::Object> as the default.
833 You can specify an alternate metaclass with the C<metaclass> parameter.
835 For more detail on this topic, see L<Moose::Cookbook::Extending::Recipe2>.
837 This method used to be documented as a function which accepted
838 positional parameters. This calling style will still work for
839 backwards compatibility, but is deprecated.
843 Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
844 and C<{into_level =E<gt> 1}>.
846 B<NOTE>: Doing this is more or less deprecated. Use L<Moose::Exporter>
847 instead, which lets you stack multiple C<Moose.pm>-alike modules
848 sanely. It handles getting the exported functions into the right place
853 An alias for C<confess>, used by internally by Moose.
861 It should be noted that C<super> and C<inner> B<cannot> be used in the same
862 method. However, they may be combined within the same class hierarchy; see
863 F<t/014_override_augment_inner_super.t> for an example.
865 The reason for this is that C<super> is only valid within a method
866 with the C<override> modifier, and C<inner> will never be valid within an
867 C<override> method. In fact, C<augment> will skip over any C<override> methods
868 when searching for its appropriate C<inner>.
870 This might seem like a restriction, but I am of the opinion that keeping these
871 two features separate (yet interoperable) actually makes them easy to use, since
872 their behavior is then easier to predict. Time will tell whether I am right or
873 not (UPDATE: so far so good).
877 =head1 ACKNOWLEDGEMENTS
881 =item I blame Sam Vilain for introducing me to the insanity that is meta-models.
883 =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6.
885 =item Without Yuval "nothingmuch" Kogman this module would not be possible,
886 and it certainly wouldn't have this name ;P
888 =item The basis of the TypeContraints module was Rob Kinyon's idea
889 originally, I just ran with it.
891 =item Thanks to mst & chansen and the whole #moose posse for all the
892 early ideas/feature-requests/encouragement/bug-finding.
894 =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes.
902 =item L<http://www.iinteractive.com/moose>
904 This is the official web home of Moose, it contains links to our public SVN repo
905 as well as links to a number of talks and articles on Moose and Moose related
908 =item L<Moose::Cookbook> - How to cook a Moose
910 =item The Moose is flying, a tutorial by Randal Schwartz
912 Part 1 - L<http://www.stonehenge.com/merlyn/LinuxMag/col94.html>
914 Part 2 - L<http://www.stonehenge.com/merlyn/LinuxMag/col95.html>
916 =item L<Class::MOP> documentation
918 =item The #moose channel on irc.perl.org
920 =item The Moose mailing list - moose@perl.org
922 =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/moose>
924 =item Several Moose extension modules in the C<MooseX::> namespace.
926 See L<http://search.cpan.org/search?query=MooseX::> for extensions.
934 =item The Art of the MetaObject Protocol
936 I mention this in the L<Class::MOP> docs too, this book was critical in
937 the development of both modules and is highly recommended.
945 =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf>
947 This paper (suggested by lbr on #moose) was what lead to the implementation
948 of the C<super>/C<override> and C<inner>/C<augment> features. If you really
949 want to understand them, I suggest you read this.
955 All complex software has bugs lurking in it, and this module is no
956 exception. If you find a bug please either email me, or add the bug
959 =head1 FEATURE REQUESTS
961 We are very strict about what features we add to the Moose core, especially
962 the user-visible features. Instead we have made sure that the underlying
963 meta-system of Moose is as extensible as possible so that you can add your
964 own features easily. That said, occasionally there is a feature needed in the
965 meta-system to support your planned extension, in which case you should
966 either email the mailing list or join us on irc at #moose to discuss.
970 Stevan Little E<lt>stevan@iinteractive.comE<gt>
972 B<with contributions from:>
978 Anders (Debolaz) Nor Berle
980 Nathan (kolibre) Gray
982 Christian (chansen) Hansen
984 Hans Dieter (confound) Pearcey
986 Eric (ewilhelm) Wilhelm
988 Guillermo (groditi) Roditi
990 Jess (castaway) Robinson
994 Robert (phaylon) Sedlacek
998 Scott (konobi) McWhirter
1000 Shlomi (rindolf) Fish
1002 Yuval (nothingmuch) Kogman
1004 Chris (perigrin) Prather
1006 Wallace (wreis) Reis
1008 Jonathan (jrockway) Rockway
1010 Dave (autarch) Rolsky
1012 Piotr (dexter) Roszatycki
1014 Sam (mugwump) Vilain
1016 Shawn (sartak) Moore
1018 ... and many other #moose folks
1020 =head1 COPYRIGHT AND LICENSE
1022 Copyright 2006-2008 by Infinity Interactive, Inc.
1024 L<http://www.iinteractive.com>
1026 This library is free software; you can redistribute it and/or modify
1027 it under the same terms as Perl itself.