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;
42 croak "Must derive at least one class" unless @_;
45 foreach my $super (@supers) {
46 Class::MOP::load_class($super);
47 croak "You cannot inherit from a Moose Role ($super)"
48 if $super->can('meta') &&
49 blessed $super->meta &&
50 $super->meta->isa('Moose::Meta::Role')
55 # this checks the metaclass to make sure
56 # it is correct, sometimes it can get out
57 # of sync when the classes are being built
58 my $meta = Moose::Meta::Class->initialize($class)->_fix_metaclass_incompatability(@supers);
59 $meta->superclasses(@supers);
64 Moose::Util::apply_all_roles(Class::MOP::Class->initialize($class), @_);
70 croak 'Usage: has \'name\' => ( key => value, ... )' if @_ == 1;
72 my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ];
73 Class::MOP::Class->initialize($class)->add_attribute( $_, %options ) for @$attrs;
78 Moose::Util::add_method_modifier($class, 'before', \@_);
83 Moose::Util::add_method_modifier($class, 'after', \@_);
88 Moose::Util::add_method_modifier($class, 'around', \@_);
92 return unless our $SUPER_BODY; $SUPER_BODY->(our @SUPER_ARGS);
97 my ( $name, $method ) = @_;
98 Class::MOP::Class->initialize($class)->add_override_method_modifier( $name => $method );
103 our ( %INNER_BODY, %INNER_ARGS );
105 if ( my $body = $INNER_BODY{$pkg} ) {
106 my @args = @{ $INNER_ARGS{$pkg} };
107 local $INNER_ARGS{$pkg};
108 local $INNER_BODY{$pkg};
109 return $body->(@args);
117 my ( $name, $method ) = @_;
118 Class::MOP::Class->initialize($class)->add_augment_method_modifier( $name => $method );
123 cluck "The make_immutable keyword has been deprecated, " .
124 "please go back to __PACKAGE__->meta->make_immutable\n";
125 Class::MOP::Class->initialize($class)->make_immutable(@_);
128 Moose::Exporter->setup_import_methods(
130 qw( extends with has before after around override augment make_immutable )
135 \&Scalar::Util::blessed,
140 # This used to be called as a function. This hack preserves
141 # backwards compatibility.
142 if ( $_[0] ne __PACKAGE__ ) {
143 return __PACKAGE__->init_meta(
153 my $class = $args{for_class}
154 or confess "Cannot call init_meta without specifying a for_class";
155 my $base_class = $args{base_class} || 'Moose::Object';
156 my $metaclass = $args{metaclass} || 'Moose::Meta::Class';
159 "The Metaclass $metaclass must be a subclass of Moose::Meta::Class."
160 unless $metaclass->isa('Moose::Meta::Class');
162 # make a subtype for each Moose class
164 unless find_type_constraint($class);
168 if ( $meta = Class::MOP::get_metaclass_by_name($class) ) {
169 unless ( $meta->isa("Moose::Meta::Class") ) {
170 confess "$class already has a metaclass, but it does not inherit $metaclass ($meta)";
173 # no metaclass, no 'meta' method
175 # now we check whether our ancestors have metaclass, and if so borrow that
176 my ( undef, @isa ) = @{ $class->mro::get_linear_isa };
178 foreach my $ancestor ( @isa ) {
179 my $ancestor_meta = Class::MOP::get_metaclass_by_name($ancestor) || next;
181 my $ancestor_meta_class = ($ancestor_meta->is_immutable
182 ? $ancestor_meta->get_mutable_metaclass_name
183 : ref($ancestor_meta));
185 # if we have an ancestor metaclass that inherits $metaclass, we use
186 # that. This is like _fix_metaclass_incompatability, but we can do it now.
188 # the case of having an ancestry is not very common, but arises in
190 unless ( $metaclass->isa( $ancestor_meta_class ) ) {
191 if ( $ancestor_meta_class->isa($metaclass) ) {
192 $metaclass = $ancestor_meta_class;
197 $meta = $metaclass->initialize($class);
200 if ( $class->can('meta') ) {
201 # check 'meta' method
203 # it may be inherited
206 # this is the case where the metaclass pragma
207 # was used before the 'use Moose' statement to
208 # override a specific class
209 my $method_meta = $class->meta;
211 ( blessed($method_meta) && $method_meta->isa('Moose::Meta::Class') )
212 || confess "$class already has a &meta function, but it does not return a Moose::Meta::Class ($meta)";
214 $meta = $method_meta;
217 unless ( $meta->has_method("meta") ) { # don't overwrite
218 # also check for inherited non moose 'meta' method?
219 # FIXME also skip this if the user requested by passing an option
222 # re-initialize so it inherits properly
223 $metaclass->initialize( ref($_[0]) || $_[0] );
228 # make sure they inherit from Moose::Object
229 $meta->superclasses($base_class)
230 unless $meta->superclasses();
235 # This may be used in some older MooseX extensions.
237 goto &Moose::Exporter::_get_caller;
240 ## make 'em all immutable
242 $_->meta->make_immutable(
243 inline_constructor => 1,
244 constructor_name => "_new",
245 inline_accessors => 1, # these are Class::MOP accessors, so they need inlining
248 Moose::Meta::Attribute
250 Moose::Meta::Instance
252 Moose::Meta::TypeConstraint
253 Moose::Meta::TypeConstraint::Union
254 Moose::Meta::TypeConstraint::Parameterized
255 Moose::Meta::TypeConstraint::Parameterizable
256 Moose::Meta::TypeConstraint::Enum
257 Moose::Meta::TypeConstraint::Class
258 Moose::Meta::TypeConstraint::Role
259 Moose::Meta::TypeConstraint::Registry
260 Moose::Meta::TypeCoercion
261 Moose::Meta::TypeCoercion::Union
264 Moose::Meta::Method::Accessor
265 Moose::Meta::Method::Constructor
266 Moose::Meta::Method::Destructor
267 Moose::Meta::Method::Overriden
268 Moose::Meta::Method::Augmented
271 Moose::Meta::Role::Method
272 Moose::Meta::Role::Method::Required
274 Moose::Meta::Role::Composite
276 Moose::Meta::Role::Application
277 Moose::Meta::Role::Application::RoleSummation
278 Moose::Meta::Role::Application::ToClass
279 Moose::Meta::Role::Application::ToRole
280 Moose::Meta::Role::Application::ToInstance
291 Moose - A postmodern object system for Perl 5
296 use Moose; # automatically turns on strict and warnings
298 has 'x' => (is => 'rw', isa => 'Int');
299 has 'y' => (is => 'rw', isa => 'Int');
312 has 'z' => (is => 'rw', isa => 'Int');
314 after 'clear' => sub {
321 Moose is an extension of the Perl 5 object system.
323 The main goal of Moose is to make Perl 5 Object Oriented programming
324 easier, more consistent and less tedious. With Moose you can to think
325 more about what you want to do and less about the mechanics of OOP.
327 Additionally, Moose is built on top of L<Class::MOP>, which is a
328 metaclass system for Perl 5. This means that Moose not only makes
329 building normal Perl 5 objects better, but it provides the power of
330 metaclass programming as well.
334 If you're new to Moose, the best place to start is the L<Moose::Intro>
335 docs, followed by the L<Moose::Cookbook>. The intro will show you what
336 Moose is, and how it makes Perl 5 OO better.
338 The cookbook recipes on Moose basics will get you up to speed with
339 many of Moose's features quickly. Once you have an idea of what Moose
340 can do, you can use the API documentation to get more detail on
341 features which interest you.
343 =head2 Moose Extensions
345 The C<MooseX::> namespace is the official place to find Moose extensions.
346 These extensions can be found on the CPAN. The easiest way to find them
347 is to search for them (L<http://search.cpan.org/search?query=MooseX::>),
348 or to examine L<Task::Moose> which aims to keep an up-to-date, easily
349 installable list of Moose extensions.
351 =head1 BUILDING CLASSES WITH MOOSE
353 Moose makes every attempt to provide as much convenience as possible during
354 class construction/definition, but still stay out of your way if you want it
355 to. Here are a few items to note when building classes with Moose.
357 Unless specified with C<extends>, any class which uses Moose will
358 inherit from L<Moose::Object>.
360 Moose will also manage all attributes (including inherited ones) that are
361 defined with C<has>. And (assuming you call C<new>, which is inherited from
362 L<Moose::Object>) this includes properly initializing all instance slots,
363 setting defaults where appropriate, and performing any type constraint checking
366 =head1 PROVIDED METHODS
368 Moose provides a number of methods to all your classes, mostly through the
369 inheritance of L<Moose::Object>. There is however, one exception.
375 This is a method which provides access to the current class's metaclass.
379 =head1 EXPORTED FUNCTIONS
381 Moose will export a number of functions into the class's namespace which
382 may then be used to set up the class. These functions all work directly
383 on the current class.
387 =item B<extends (@superclasses)>
389 This function will set the superclass(es) for the current class.
391 This approach is recommended instead of C<use base>, because C<use base>
392 actually C<push>es onto the class's C<@ISA>, whereas C<extends> will
393 replace it. This is important to ensure that classes which do not have
394 superclasses still properly inherit from L<Moose::Object>.
396 =item B<with (@roles)>
398 This will apply a given set of C<@roles> to the local class.
400 =item B<has $name =E<gt> %options>
402 This will install an attribute of a given C<$name> into the current class.
403 The C<%options> are the same as those provided by
404 L<Class::MOP::Attribute>, in addition to the list below which are provided
405 by Moose (L<Moose::Meta::Attribute> to be more specific):
409 =item I<is =E<gt> 'rw'|'ro'>
411 The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read
412 only). These will create either a read/write accessor or a read-only
413 accessor respectively, using the same name as the C<$name> of the attribute.
415 If you need more control over how your accessors are named, you can use the
416 I<reader>, I<writer> and I<accessor> options inherited from
417 L<Class::MOP::Attribute>, however if you use those, you won't need the I<is>
420 =item I<isa =E<gt> $type_name>
422 The I<isa> option uses Moose's type constraint facilities to set up runtime
423 type checking for this attribute. Moose will perform the checks during class
424 construction, and within any accessors. The C<$type_name> argument must be a
425 string. The string may be either a class name or a type defined using
426 Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
427 for information on how to define a new type, and how to retrieve type meta-data).
429 =item I<coerce =E<gt> (1|0)>
431 This will attempt to use coercion with the supplied type constraint to change
432 the value passed into any accessors or constructors. You B<must> have supplied
433 a type constraint in order for this to work. See L<Moose::Cookbook::Basics::Recipe5>
436 =item I<does =E<gt> $role_name>
438 This will accept the name of a role which the value stored in this attribute
439 is expected to have consumed.
441 =item I<required =E<gt> (1|0)>
443 This marks the attribute as being required. This means a I<defined> value must be
444 supplied during class construction, and the attribute may never be set to
445 C<undef> with an accessor.
447 =item I<weak_ref =E<gt> (1|0)>
449 This will tell the class to store the value of this attribute as a weakened
450 reference. If an attribute is a weakened reference, it B<cannot> also be
453 =item I<lazy =E<gt> (1|0)>
455 This will tell the class to not create this slot until absolutely necessary.
456 If an attribute is marked as lazy it B<must> have a default supplied.
458 =item I<auto_deref =E<gt> (1|0)>
460 This tells the accessor whether to automatically dereference the value returned.
461 This is only legal if your C<isa> option is either C<ArrayRef> or C<HashRef>.
463 =item I<trigger =E<gt> $code>
465 The I<trigger> option is a CODE reference which will be called after the value of
466 the attribute is set. The CODE ref will be passed the instance itself, the
467 updated value and the attribute meta-object (this is for more advanced fiddling
468 and can typically be ignored). You B<cannot> have a trigger on a read-only
471 =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
473 The I<handles> option provides Moose classes with automated delegation features.
474 This is a pretty complex and powerful option. It accepts many different option
475 formats, each with its own benefits and drawbacks.
477 B<NOTE:> The class being delegated to does not need to be a Moose based class,
478 which is why this feature is especially useful when wrapping non-Moose classes.
480 All I<handles> option formats share the following traits:
482 You cannot override a locally defined method with a delegated method; an
483 exception will be thrown if you try. That is to say, if you define C<foo> in
484 your class, you cannot override it with a delegated C<foo>. This is almost never
485 something you would want to do, and if it is, you should do it by hand and not
488 You cannot override any of the methods found in Moose::Object, or the C<BUILD>
489 and C<DEMOLISH> methods. These will not throw an exception, but will silently
490 move on to the next method in the list. My reasoning for this is that you would
491 almost never want to do this, since it usually breaks your class. As with
492 overriding locally defined methods, if you do want to do this, you should do it
493 manually, not with Moose.
495 You do not I<need> to have a reader (or accessor) for the attribute in order
496 to delegate to it. Moose will create a means of accessing the value for you,
497 however this will be several times B<less> efficient then if you had given
498 the attribute a reader (or accessor) to use.
500 Below is the documentation for each option format:
506 This is the most common usage for I<handles>. You basically pass a list of
507 method names to be delegated, and Moose will install a delegation method
512 This is the second most common usage for I<handles>. Instead of a list of
513 method names, you pass a HASH ref where each key is the method name you
514 want installed locally, and its value is the name of the original method
515 in the class being delegated to.
517 This can be very useful for recursive classes like trees. Here is a
518 quick example (soon to be expanded into a Moose::Cookbook recipe):
523 has 'node' => (is => 'rw', isa => 'Any');
528 default => sub { [] }
536 parent_node => 'node',
537 siblings => 'children',
541 In this example, the Tree package gets C<parent_node> and C<siblings> methods,
542 which delegate to the C<node> and C<children> methods (respectively) of the Tree
543 instance stored in the C<parent> slot.
547 The regexp option works very similar to the ARRAY option, except that it builds
548 the list of methods for you. It starts by collecting all possible methods of the
549 class being delegated to, then filters that list using the regexp supplied here.
551 B<NOTE:> An I<isa> option is required when using the regexp option format. This
552 is so that we can determine (at compile time) the method list from the class.
553 Without an I<isa> this is just not possible.
557 With the role option, you specify the name of a role whose "interface" then
558 becomes the list of methods to handle. The "interface" can be defined as; the
559 methods of the role and any required methods of the role. It should be noted
560 that this does B<not> include any method modifiers or generated attribute
561 methods (which is consistent with role composition).
565 This is the option to use when you really want to do something funky. You should
566 only use it if you really know what you are doing, as it involves manual
569 This takes a code reference, which should expect two arguments. The first is the
570 attribute meta-object this I<handles> is attached to. The second is the
571 metaclass of the class being delegated to. It expects you to return a hash (not
572 a HASH ref) of the methods you want mapped.
576 =item I<metaclass =E<gt> $metaclass_name>
578 This tells the class to use a custom attribute metaclass for this particular
579 attribute. Custom attribute metaclasses are useful for extending the
580 capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
581 but they are still a fairly advanced topic and too much to cover here, see
582 L<Moose::Cookbook::Meta::Recipe1> for more information.
584 The default behavior here is to just load C<$metaclass_name>; however, we also
585 have a way to alias to a shorter name. This will first look to see if
586 B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose
587 will then check to see if that has the method C<register_implementation>, which
588 should return the actual name of the custom attribute metaclass. If there is no
589 C<register_implementation> method, it will fall back to using
590 B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name.
592 =item I<traits =E<gt> [ @role_names ]>
594 This tells Moose to take the list of C<@role_names> and apply them to the
595 attribute meta-object. This is very similar to the I<metaclass> option, but
596 allows you to use more than one extension at a time.
598 See L<TRAIT NAME RESOLUTION> for details on how a trait name is
599 resolved to a class name.
601 Also see L<Moose::Cookbook::Meta::Recipe3> for a metaclass trait
606 =item B<has +$name =E<gt> %options>
608 This is variation on the normal attibute creator C<has> which allows you to
609 clone and extend an attribute from a superclass or from a role. Here is an
610 example of the superclass usage:
618 default => 'Hello, I am a Foo'
626 has '+message' => (default => 'Hello I am My::Foo');
628 What is happening here is that B<My::Foo> is cloning the C<message> attribute
629 from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt>
630 'Str'> characteristics, but changing the value in C<default>.
632 Here is another example, but within the context of a role:
640 default => 'Hello, I am a Foo'
648 has '+message' => (default => 'Hello I am My::Foo');
650 In this case, we are basically taking the attribute which the role supplied
651 and altering it within the bounds of this feature.
653 Aside from where the attributes come from (one from superclass, the other
654 from a role), this feature works exactly the same. This feature is restricted
655 somewhat, so as to try and force at least I<some> sanity into it. You are only
656 allowed to change the following attributes:
662 Change the default value of an attribute.
666 Change whether the attribute attempts to coerce a value passed to it.
670 Change if the attribute is required to have a value.
672 =item I<documentation>
674 Change the documentation string associated with the attribute.
678 Change if the attribute lazily initializes the slot.
682 You I<are> allowed to change the type without restriction.
684 It is recommended that you use this freedom with caution. We used to
685 only allow for extension only if the type was a subtype of the parent's
686 type, but we felt that was too restrictive and is better left as a
691 You are allowed to B<add> a new C<handles> definition, but you are B<not>
692 allowed to I<change> one.
696 You are allowed to B<add> a new C<builder> definition, but you are B<not>
697 allowed to I<change> one.
701 You are allowed to B<add> a new C<metaclass> definition, but you are
702 B<not> allowed to I<change> one.
706 You are allowed to B<add> additional traits to the C<traits> definition.
707 These traits will be composed into the attribute, but pre-existing traits
708 B<are not> overridden, or removed.
712 =item B<before $name|@names =E<gt> sub { ... }>
714 =item B<after $name|@names =E<gt> sub { ... }>
716 =item B<around $name|@names =E<gt> sub { ... }>
718 This three items are syntactic sugar for the before, after, and around method
719 modifier features that L<Class::MOP> provides. More information on these may be
720 found in the L<Class::MOP::Class documentation|Class::MOP::Class/"Method
725 The keyword C<super> is a no-op when called outside of an C<override> method. In
726 the context of an C<override> method, it will call the next most appropriate
727 superclass method with the same arguments as the original method.
729 =item B<override ($name, &sub)>
731 An C<override> method is a way of explicitly saying "I am overriding this
732 method from my superclass". You can call C<super> within this method, and
733 it will work as expected. The same thing I<can> be accomplished with a normal
734 method call and the C<SUPER::> pseudo-package; it is really your choice.
738 The keyword C<inner>, much like C<super>, is a no-op outside of the context of
739 an C<augment> method. You can think of C<inner> as being the inverse of
740 C<super>; the details of how C<inner> and C<augment> work is best described in
741 the L<Moose::Cookbook::Basics::Recipe6>.
743 =item B<augment ($name, &sub)>
745 An C<augment> method, is a way of explicitly saying "I am augmenting this
746 method from my superclass". Once again, the details of how C<inner> and
747 C<augment> work is best described in the L<Moose::Cookbook::Basics::Recipe6>.
751 This is the C<Carp::confess> function, and exported here because I use it
756 This is the C<Scalar::Util::blessed> function, it is exported here because I
757 use it all the time. It is highly recommended that this is used instead of
758 C<ref> anywhere you need to test for an object's class name.
762 =head1 METACLASS TRAITS
764 When you use Moose, you can also specify traits which will be applied
767 use Moose -traits => 'My::Trait';
769 This is very similar to the attribute traits feature. When you do
770 this, your class's C<meta> object will have the specified traits
771 applied to it. See L<TRAIT NAME RESOLUTION> for more details.
773 =head1 TRAIT NAME RESOLUTION
775 By default, when given a trait name, Moose simply tries to load a
776 class of the same name. If such a class does not exist, it then looks
777 for for a class matching
778 B<Moose::Meta::$type::Custom::Trait::$trait_name>. The C<$type>
779 variable here will be one of B<Attribute> or B<Class>, depending on
780 what the trait is being applied to.
782 If a class with this long name exists, Moose checks to see if it has
783 the method C<register_implementation>. This method is expected to
784 return the I<real> class name of the trait. If there is no
785 C<register_implementation> method, it will fall back to using
786 B<Moose::Meta::$type::Custom::Trait::$trait> as the trait name.
788 If all this is confusing, take a look at
789 L<Moose::Cookbook::Meta::Recipe3>, which demonstrates how to create an
792 =head1 UNIMPORTING FUNCTIONS
796 Moose offers a way to remove the keywords it exports, through the C<unimport>
797 method. You simply have to say C<no Moose> at the bottom of your code for this
798 to work. Here is an example:
803 has 'first_name' => (is => 'rw', isa => 'Str');
804 has 'last_name' => (is => 'rw', isa => 'Str');
808 $self->first_name . ' ' . $self->last_name
811 no Moose; # keywords are removed from the Person package
813 =head1 EXTENDING AND EMBEDDING MOOSE
815 Moose also offers some options for extending or embedding it into your
816 own framework. To learn more about extending Moose, we recommend
817 checking out the "Extending" recipes in the L<Moose::Cookbook>,
818 starting with L<Moose::Cookbook::Extending::Recipe1>, which provides
819 an overview of all the different ways you might extend Moose.
821 =head2 B<< Moose->init_meta(for_class => $class, base_class => $baseclass, metaclass => $metaclass) >>
823 The C<init_meta> method sets up the metaclass object for the class
824 specified by C<for_class>. This method injects a a C<meta> accessor
825 into the class so you can get at this object. It also sets the class's
826 superclass to C<base_class>, with L<Moose::Object> as the default.
828 You can specify an alternate metaclass with the C<metaclass> parameter.
830 For more detail on this topic, see L<Moose::Cookbook::Extending::Recipe2>.
832 This method used to be documented as a function which accepted
833 positional parameters. This calling style will still work for
834 backwards compatibility, but is deprecated.
838 Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
839 and C<{into_level =E<gt> 1}>.
841 B<NOTE>: Doing this is more or less deprecated. Use L<Moose::Exporter>
842 instead, which lets you stack multiple C<Moose.pm>-alike modules
843 sanely. It handles getting the exported functions into the right place
852 It should be noted that C<super> and C<inner> B<cannot> be used in the same
853 method. However, they may be combined within the same class hierarchy; see
854 F<t/014_override_augment_inner_super.t> for an example.
856 The reason for this is that C<super> is only valid within a method
857 with the C<override> modifier, and C<inner> will never be valid within an
858 C<override> method. In fact, C<augment> will skip over any C<override> methods
859 when searching for its appropriate C<inner>.
861 This might seem like a restriction, but I am of the opinion that keeping these
862 two features separate (yet interoperable) actually makes them easy to use, since
863 their behavior is then easier to predict. Time will tell whether I am right or
864 not (UPDATE: so far so good).
868 =head1 ACKNOWLEDGEMENTS
872 =item I blame Sam Vilain for introducing me to the insanity that is meta-models.
874 =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6.
876 =item Without Yuval "nothingmuch" Kogman this module would not be possible,
877 and it certainly wouldn't have this name ;P
879 =item The basis of the TypeContraints module was Rob Kinyon's idea
880 originally, I just ran with it.
882 =item Thanks to mst & chansen and the whole #moose posse for all the
883 early ideas/feature-requests/encouragement/bug-finding.
885 =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes.
893 =item L<http://www.iinteractive.com/moose>
895 This is the official web home of Moose, it contains links to our public SVN repo
896 as well as links to a number of talks and articles on Moose and Moose related
899 =item L<Moose::Cookbook> - How to cook a Moose
901 =item The Moose is flying, a tutorial by Randal Schwartz
903 Part 1 - L<http://www.stonehenge.com/merlyn/LinuxMag/col94.html>
905 Part 2 - L<http://www.stonehenge.com/merlyn/LinuxMag/col95.html>
907 =item L<Class::MOP> documentation
909 =item The #moose channel on irc.perl.org
911 =item The Moose mailing list - moose@perl.org
913 =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/moose>
915 =item Several Moose extension modules in the C<MooseX::> namespace.
917 See L<http://search.cpan.org/search?query=MooseX::> for extensions.
925 =item The Art of the MetaObject Protocol
927 I mention this in the L<Class::MOP> docs too, this book was critical in
928 the development of both modules and is highly recommended.
936 =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf>
938 This paper (suggested by lbr on #moose) was what lead to the implementation
939 of the C<super>/C<override> and C<inner>/C<augment> features. If you really
940 want to understand them, I suggest you read this.
946 All complex software has bugs lurking in it, and this module is no
947 exception. If you find a bug please either email me, or add the bug
950 =head1 FEATURE REQUESTS
952 We are very strict about what features we add to the Moose core, especially
953 the user-visible features. Instead we have made sure that the underlying
954 meta-system of Moose is as extensible as possible so that you can add your
955 own features easily. That said, occasionally there is a feature needed in the
956 meta-system to support your planned extension, in which case you should
957 either email the mailing list or join us on irc at #moose to discuss.
961 Stevan Little E<lt>stevan@iinteractive.comE<gt>
963 B<with contributions from:>
969 Anders (Debolaz) Nor Berle
971 Nathan (kolibre) Gray
973 Christian (chansen) Hansen
975 Hans Dieter (confound) Pearcey
977 Eric (ewilhelm) Wilhelm
979 Guillermo (groditi) Roditi
981 Jess (castaway) Robinson
985 Robert (phaylon) Sedlacek
989 Scott (konobi) McWhirter
991 Shlomi (rindolf) Fish
993 Yuval (nothingmuch) Kogman
995 Chris (perigrin) Prather
999 Jonathan (jrockway) Rockway
1001 Dave (autarch) Rolsky
1003 Piotr (dexter) Roszatycki
1005 Sam (mugwump) Vilain
1007 Shawn (sartak) Moore
1009 ... and many other #moose folks
1011 =head1 COPYRIGHT AND LICENSE
1013 Copyright 2006-2008 by Infinity Interactive, Inc.
1015 L<http://www.iinteractive.com>
1017 This library is free software; you can redistribute it and/or modify
1018 it under the same terms as Perl itself.