8 our $AUTHORITY = 'cpan:STEVAN';
10 use Scalar::Util 'blessed', 'reftype';
11 use Carp 'confess', 'croak', 'cluck';
18 use Moose::Meta::Class;
19 use Moose::Meta::TypeConstraint;
20 use Moose::Meta::TypeCoercion;
21 use Moose::Meta::Attribute;
22 use Moose::Meta::Instance;
24 use Moose::Meta::Role;
27 use Moose::Util::TypeConstraints;
34 my ( $class, $base_class, $metaclass ) = @_;
35 $base_class = 'Moose::Object' unless defined $base_class;
36 $metaclass = 'Moose::Meta::Class' unless defined $metaclass;
39 "The Metaclass $metaclass must be a subclass of Moose::Meta::Class."
40 unless $metaclass->isa('Moose::Meta::Class');
42 # make a subtype for each Moose class
44 unless find_type_constraint($class);
47 if ( $class->can('meta') ) {
49 # this is the case where the metaclass pragma
50 # was used before the 'use Moose' statement to
51 # override a specific class
52 $meta = $class->meta();
53 ( blessed($meta) && $meta->isa('Moose::Meta::Class') )
54 || confess "You already have a &meta function, but it does not return a Moose::Meta::Class";
58 # this is broken currently, we actually need
59 # to allow the possiblity of an inherited
60 # meta, which will not be visible until the
61 # user 'extends' first. This needs to have
62 # more intelligence to it
63 $meta = $metaclass->initialize($class);
66 # re-initialize so it inherits properly
67 $metaclass->initialize( blessed( $_[0] ) || $_[0] );
72 # make sure they inherit from Moose::Object
73 $meta->superclasses($base_class)
74 unless $meta->superclasses();
82 return Class::MOP::subname('Moose::extends' => sub (@) {
83 confess "Must derive at least one class" unless @_;
86 foreach my $super (@supers) {
87 Class::MOP::load_class($super);
90 # this checks the metaclass to make sure
91 # it is correct, sometimes it can get out
92 # of sync when the classes are being built
93 my $meta = $class->meta->_fix_metaclass_incompatability(@supers);
94 $meta->superclasses(@supers);
99 return Class::MOP::subname('Moose::with' => sub (@) {
100 Moose::Util::apply_all_roles($class->meta, @_)
105 return Class::MOP::subname('Moose::has' => sub ($;%) {
107 croak 'Usage: has \'name\' => ( key => value, ... )' if @_ == 1;
109 my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ];
110 $class->meta->add_attribute( $_, %options ) for @$attrs;
115 return Class::MOP::subname('Moose::before' => sub (@&) {
117 my $meta = $class->meta;
118 $meta->add_before_method_modifier( $_, $code ) for @_;
123 return Class::MOP::subname('Moose::after' => sub (@&) {
125 my $meta = $class->meta;
126 $meta->add_after_method_modifier( $_, $code ) for @_;
131 return Class::MOP::subname('Moose::around' => sub (@&) {
133 my $meta = $class->meta;
134 $meta->add_around_method_modifier( $_, $code ) for @_;
138 # FIXME can be made into goto, might break caller() for existing code
139 return Class::MOP::subname('Moose::super' => sub { return unless our $SUPER_BODY; $SUPER_BODY->(our @SUPER_ARGS) })
142 # return subname 'Moose::next' => sub { @_ = our @SUPER_ARGS; goto \&next::method };
146 return Class::MOP::subname('Moose::override' => sub ($&) {
147 my ( $name, $method ) = @_;
148 $class->meta->add_override_method_modifier( $name => $method );
152 return Class::MOP::subname('Moose::inner' => sub {
154 our ( %INNER_BODY, %INNER_ARGS );
156 if ( my $body = $INNER_BODY{$pkg} ) {
157 my @args = @{ $INNER_ARGS{$pkg} };
158 local $INNER_ARGS{$pkg};
159 local $INNER_BODY{$pkg};
160 return $body->(@args);
168 return Class::MOP::subname('Moose::augment' => sub (@&) {
169 my ( $name, $method ) = @_;
170 $class->meta->add_augment_method_modifier( $name => $method );
173 make_immutable => sub {
175 return Class::MOP::subname('Moose::make_immutable' => sub {
176 cluck "The make_immutable keyword has been deprecated, " .
177 "please go back to __PACKAGE__->meta->make_immutable\n";
178 $class->meta->make_immutable(@_);
182 return \&Carp::confess;
185 return \&Scalar::Util::blessed;
189 my $exporter = Sub::Exporter::build_exporter(
191 exports => \%exports,
192 groups => { default => [':all'] }
196 # 1 extra level because it's called by import so there's a layer of indirection
200 ref $_[1] && defined $_[1]->{into}
202 : ref $_[1] && defined $_[1]->{into_level}
203 ? caller($offset + $_[1]->{into_level})
208 $CALLER = _get_caller(@_);
210 # this works because both pragmas set $^H (see perldoc perlvar)
211 # which affects the current compilation - i.e. the file who use'd
212 # us - which is why we don't need to do anything special to make
213 # it affect that file rather than this one (which is already compiled)
218 # we should never export to main
219 return if $CALLER eq 'main';
221 init_meta( $CALLER, 'Moose::Object' );
228 my $class = _get_caller(@_);
230 # loop through the exports ...
231 foreach my $name ( keys %exports ) {
234 if ( defined &{ $class . '::' . $name } ) {
235 my $keyword = \&{ $class . '::' . $name };
237 # make sure it is from Moose
238 my ($pkg_name) = Class::MOP::get_code_info($keyword);
239 next if $pkg_name ne 'Moose';
241 # and if it is from Moose then undef the slot
242 delete ${ $class . '::' }{$name};
249 ## make 'em all immutable
251 $_->meta->make_immutable(
252 inline_constructor => 0,
253 inline_accessors => 1, # these are Class::MOP accessors, so they need inlining
256 'Moose::Meta::Attribute',
257 'Moose::Meta::Class',
258 'Moose::Meta::Instance',
260 'Moose::Meta::TypeConstraint',
261 'Moose::Meta::TypeConstraint::Union',
262 'Moose::Meta::TypeConstraint::Parameterized',
263 'Moose::Meta::TypeCoercion',
265 'Moose::Meta::Method',
266 'Moose::Meta::Method::Accessor',
267 'Moose::Meta::Method::Constructor',
268 'Moose::Meta::Method::Destructor',
269 'Moose::Meta::Method::Overriden',
272 'Moose::Meta::Role::Method',
273 'Moose::Meta::Role::Method::Required',
284 Moose - A postmodern object system for Perl 5
289 use Moose; # automatically turns on strict and warnings
291 has 'x' => (is => 'rw', isa => 'Int');
292 has 'y' => (is => 'rw', isa => 'Int');
305 has 'z' => (is => 'rw', isa => 'Int');
307 after 'clear' => sub {
314 Moose is an extension of the Perl 5 object system.
316 =head2 Another object system!?!?
318 Yes, I know there has been an explosion recently of new ways to
319 build objects in Perl 5, most of them based on inside-out objects
320 and other such things. Moose is different because it is not a new
321 object system for Perl 5, but instead an extension of the existing
324 Moose is built on top of L<Class::MOP>, which is a metaclass system
325 for Perl 5. This means that Moose not only makes building normal
326 Perl 5 objects better, but it also provides the power of metaclass
329 =head2 Is this for real? Or is this just an experiment?
331 Moose is I<based> on the prototypes and experiments I did for the Perl 6
332 meta-model. However, Moose is B<NOT> an experiment/prototype; it is for B<real>.
334 =head2 Is this ready for use in production?
336 Yes, I believe that it is.
338 Moose has been used successfully in production environemnts by several people
339 and companies (including the one I work for). There are Moose applications
340 which have been in production with little or no issue now for well over a year.
341 I consider it highly stable and we are commited to keeping it stable.
343 Of course, in the end, you need to make this call yourself. If you have
344 any questions or concerns, please feel free to email me, or even the list
345 or just stop by #moose and ask away.
347 =head2 Is Moose just Perl 6 in Perl 5?
349 No. While Moose is very much inspired by Perl 6, it is not itself Perl 6.
350 Instead, it is an OO system for Perl 5. I built Moose because I was tired of
351 writing the same old boring Perl 5 OO code, and drooling over Perl 6 OO. So
352 instead of switching to Ruby, I wrote Moose :)
354 =head2 Wait, I<post> modern, I thought it was just I<modern>?
356 So I was reading Larry Wall's talk from the 1999 Linux World entitled
357 "Perl, the first postmodern computer language" in which he talks about how
358 he picked the features for Perl because he thought they were cool and he
359 threw out the ones that he thought sucked. This got me thinking about how
360 we have done the same thing in Moose. For Moose, we have "borrowed" features
361 from Perl 6, CLOS (LISP), Smalltalk, Java, BETA, OCaml, Ruby and more, and
362 the bits we didn't like (cause they sucked) we tossed aside. So for this
363 reason (and a few others) I have re-dubbed Moose a I<postmodern> object system.
367 =head2 Moose Extensions
369 The L<MooseX::> namespace is the official place to find Moose extensions.
370 There are a number of these modules out on CPAN right now the best way to
371 find them is to search for MooseX:: on search.cpan.org.
373 =head1 BUILDING CLASSES WITH MOOSE
375 Moose makes every attempt to provide as much convenience as possible during
376 class construction/definition, but still stay out of your way if you want it
377 to. Here are a few items to note when building classes with Moose.
379 Unless specified with C<extends>, any class which uses Moose will
380 inherit from L<Moose::Object>.
382 Moose will also manage all attributes (including inherited ones) that are
383 defined with C<has>. And (assuming you call C<new>, which is inherited from
384 L<Moose::Object>) this includes properly initializing all instance slots,
385 setting defaults where appropriate, and performing any type constraint checking
388 =head1 PROVIDED METHODS
390 Moose provides a number of methods to all your classes, mostly through the
391 inheritance of L<Moose::Object>. There is however, one exception.
397 This is a method which provides access to the current class's metaclass.
401 =head1 EXPORTED FUNCTIONS
403 Moose will export a number of functions into the class's namespace which
404 may then be used to set up the class. These functions all work directly
405 on the current class.
409 =item B<extends (@superclasses)>
411 This function will set the superclass(es) for the current class.
413 This approach is recommended instead of C<use base>, because C<use base>
414 actually C<push>es onto the class's C<@ISA>, whereas C<extends> will
415 replace it. This is important to ensure that classes which do not have
416 superclasses still properly inherit from L<Moose::Object>.
418 =item B<with (@roles)>
420 This will apply a given set of C<@roles> to the local class.
422 =item B<has $name =E<gt> %options>
424 This will install an attribute of a given C<$name> into the current class.
425 The C<%options> are the same as those provided by
426 L<Class::MOP::Attribute>, in addition to the list below which are provided
427 by Moose (L<Moose::Meta::Attribute> to be more specific):
431 =item I<is =E<gt> 'rw'|'ro'>
433 The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read
434 only). These will create either a read/write accessor or a read-only
435 accessor respectively, using the same name as the C<$name> of the attribute.
437 If you need more control over how your accessors are named, you can use the
438 I<reader>, I<writer> and I<accessor> options inherited from
439 L<Class::MOP::Attribute>, however if you use those, you won't need the I<is>
442 =item I<isa =E<gt> $type_name>
444 The I<isa> option uses Moose's type constraint facilities to set up runtime
445 type checking for this attribute. Moose will perform the checks during class
446 construction, and within any accessors. The C<$type_name> argument must be a
447 string. The string may be either a class name or a type defined using
448 Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
449 for information on how to define a new type, and how to retrieve type meta-data).
451 =item I<coerce =E<gt> (1|0)>
453 This will attempt to use coercion with the supplied type constraint to change
454 the value passed into any accessors or constructors. You B<must> have supplied
455 a type constraint in order for this to work. See L<Moose::Cookbook::Recipe5>
458 =item I<does =E<gt> $role_name>
460 This will accept the name of a role which the value stored in this attribute
461 is expected to have consumed.
463 =item I<required =E<gt> (1|0)>
465 This marks the attribute as being required. This means a I<defined> value must be
466 supplied during class construction, and the attribute may never be set to
467 C<undef> with an accessor.
469 =item I<weak_ref =E<gt> (1|0)>
471 This will tell the class to store the value of this attribute as a weakened
472 reference. If an attribute is a weakened reference, it B<cannot> also be
475 =item I<lazy =E<gt> (1|0)>
477 This will tell the class to not create this slot until absolutely necessary.
478 If an attribute is marked as lazy it B<must> have a default supplied.
480 =item I<auto_deref =E<gt> (1|0)>
482 This tells the accessor whether to automatically dereference the value returned.
483 This is only legal if your C<isa> option is either C<ArrayRef> or C<HashRef>.
485 =item I<trigger =E<gt> $code>
487 The I<trigger> option is a CODE reference which will be called after the value of
488 the attribute is set. The CODE ref will be passed the instance itself, the
489 updated value and the attribute meta-object (this is for more advanced fiddling
490 and can typically be ignored). You B<cannot> have a trigger on a read-only
493 =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
495 The I<handles> option provides Moose classes with automated delegation features.
496 This is a pretty complex and powerful option. It accepts many different option
497 formats, each with its own benefits and drawbacks.
499 B<NOTE:> The class being delegated to does not need to be a Moose based class,
500 which is why this feature is especially useful when wrapping non-Moose classes.
502 All I<handles> option formats share the following traits:
504 You cannot override a locally defined method with a delegated method; an
505 exception will be thrown if you try. That is to say, if you define C<foo> in
506 your class, you cannot override it with a delegated C<foo>. This is almost never
507 something you would want to do, and if it is, you should do it by hand and not
510 You cannot override any of the methods found in Moose::Object, or the C<BUILD>
511 and C<DEMOLISH> methods. These will not throw an exception, but will silently
512 move on to the next method in the list. My reasoning for this is that you would
513 almost never want to do this, since it usually breaks your class. As with
514 overriding locally defined methods, if you do want to do this, you should do it
515 manually, not with Moose.
517 You do not I<need> to have a reader (or accessor) for the attribute in order
518 to delegate to it. Moose will create a means of accessing the value for you,
519 however this will be several times B<less> efficient then if you had given
520 the attribute a reader (or accessor) to use.
522 Below is the documentation for each option format:
528 This is the most common usage for I<handles>. You basically pass a list of
529 method names to be delegated, and Moose will install a delegation method
534 This is the second most common usage for I<handles>. Instead of a list of
535 method names, you pass a HASH ref where each key is the method name you
536 want installed locally, and its value is the name of the original method
537 in the class being delegated to.
539 This can be very useful for recursive classes like trees. Here is a
540 quick example (soon to be expanded into a Moose::Cookbook::Recipe):
545 has 'node' => (is => 'rw', isa => 'Any');
550 default => sub { [] }
558 parent_node => 'node',
559 siblings => 'children',
563 In this example, the Tree package gets C<parent_node> and C<siblings> methods,
564 which delegate to the C<node> and C<children> methods (respectively) of the Tree
565 instance stored in the C<parent> slot.
569 The regexp option works very similar to the ARRAY option, except that it builds
570 the list of methods for you. It starts by collecting all possible methods of the
571 class being delegated to, then filters that list using the regexp supplied here.
573 B<NOTE:> An I<isa> option is required when using the regexp option format. This
574 is so that we can determine (at compile time) the method list from the class.
575 Without an I<isa> this is just not possible.
579 With the role option, you specify the name of a role whose "interface" then
580 becomes the list of methods to handle. The "interface" can be defined as; the
581 methods of the role and any required methods of the role. It should be noted
582 that this does B<not> include any method modifiers or generated attribute
583 methods (which is consistent with role composition).
587 This is the option to use when you really want to do something funky. You should
588 only use it if you really know what you are doing, as it involves manual
591 This takes a code reference, which should expect two arguments. The first is the
592 attribute meta-object this I<handles> is attached to. The second is the
593 metaclass of the class being delegated to. It expects you to return a hash (not
594 a HASH ref) of the methods you want mapped.
598 =item I<metaclass =E<gt> $metaclass_name>
600 This tells the class to use a custom attribute metaclass for this particular
601 attribute. Custom attribute metaclasses are useful for extending the
602 capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
603 but they are still a fairly advanced topic and too much to cover here, see
604 L<Moose::Cookbook::Recipe11> for more information.
606 The default behavior here is to just load C<$metaclass_name>; however, we also
607 have a way to alias to a shorter name. This will first look to see if
608 B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose
609 will then check to see if that has the method C<register_implementation>, which
610 should return the actual name of the custom attribute metaclass. If there is no
611 C<register_implementation> method, it will fall back to using
612 B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name.
614 =item I<traits =E<gt> [ @role_names ]>
616 This tells Moose to take the list of C<@role_names> and apply them to the
617 attribute meta-object. This is very similar to the I<metaclass> option, but
618 allows you to use more than one extension at a time. This too is an advanced
619 topic, we don't yet have a cookbook for it though.
621 As with I<metaclass>, the default behavior is to just load C<$role_name>; however,
622 we also have a way to alias to a shorter name. This will first look to see if
623 B<Moose::Meta::Attribute::Custom::Trait::$role_name> exists. If it does, Moose
624 will then check to see if that has the method C<register_implementation>, which
625 should return the actual name of the custom attribute trait. If there is no
626 C<register_implementation> method, it will fall back to using
627 B<Moose::Meta::Attribute::Custom::Trait::$metaclass_name> as the trait name.
631 =item B<has +$name =E<gt> %options>
633 This is variation on the normal attibute creator C<has> which allows you to
634 clone and extend an attribute from a superclass or from a role. Here is an
635 example of the superclass usage:
643 default => 'Hello, I am a Foo'
651 has '+message' => (default => 'Hello I am My::Foo');
653 What is happening here is that B<My::Foo> is cloning the C<message> attribute
654 from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt>
655 'Str'> characteristics, but changing the value in C<default>.
657 Here is another example, but within the context of a role:
665 default => 'Hello, I am a Foo'
673 has '+message' => (default => 'Hello I am My::Foo');
675 In this case, we are basically taking the attribute which the role supplied
676 and altering it within the bounds of this feature.
678 Aside from where the attributes come from (one from superclass, the other
679 from a role), this feature works exactly the same. This feature is restricted
680 somewhat, so as to try and force at least I<some> sanity into it. You are only
681 allowed to change the following attributes:
687 Change the default value of an attribute.
691 Change whether the attribute attempts to coerce a value passed to it.
695 Change if the attribute is required to have a value.
697 =item I<documentation>
699 Change the documentation string associated with the attribute.
703 Change if the attribute lazily initializes the slot.
707 You I<are> allowed to change the type without restriction.
709 It is recommended that you use this freedom with caution. We used to
710 only allow for extension only if the type was a subtype of the parent's
711 type, but we felt that was too restrictive and is better left as a
716 You are allowed to B<add> a new C<handles> definition, but you are B<not>
717 allowed to I<change> one.
721 You are allowed to B<add> a new C<builder> definition, but you are B<not>
722 allowed to I<change> one.
726 You are allowed to B<add> a new C<metaclass> definition, but you are
727 B<not> allowed to I<change> one.
731 You are allowed to B<add> additional traits to the C<traits> definition.
732 These traits will be composed into the attribute, but pre-existing traits
733 B<are not> overridden, or removed.
737 =item B<before $name|@names =E<gt> sub { ... }>
739 =item B<after $name|@names =E<gt> sub { ... }>
741 =item B<around $name|@names =E<gt> sub { ... }>
743 This three items are syntactic sugar for the before, after, and around method
744 modifier features that L<Class::MOP> provides. More information on these may be
745 found in the L<Class::MOP::Class documentation|Class::MOP::Class/"Method
750 The keyword C<super> is a no-op when called outside of an C<override> method. In
751 the context of an C<override> method, it will call the next most appropriate
752 superclass method with the same arguments as the original method.
754 =item B<override ($name, &sub)>
756 An C<override> method is a way of explicitly saying "I am overriding this
757 method from my superclass". You can call C<super> within this method, and
758 it will work as expected. The same thing I<can> be accomplished with a normal
759 method call and the C<SUPER::> pseudo-package; it is really your choice.
763 The keyword C<inner>, much like C<super>, is a no-op outside of the context of
764 an C<augment> method. You can think of C<inner> as being the inverse of
765 C<super>; the details of how C<inner> and C<augment> work is best described in
766 the L<Moose::Cookbook::Recipe7>.
768 =item B<augment ($name, &sub)>
770 An C<augment> method, is a way of explicitly saying "I am augmenting this
771 method from my superclass". Once again, the details of how C<inner> and
772 C<augment> work is best described in the L<Moose::Cookbook::Recipe7>.
776 This is the C<Carp::confess> function, and exported here because I use it
781 This is the C<Scalar::Util::blessed> function, it is exported here because I
782 use it all the time. It is highly recommended that this is used instead of
783 C<ref> anywhere you need to test for an object's class name.
787 =head1 UNIMPORTING FUNCTIONS
791 Moose offers a way to remove the keywords it exports, through the C<unimport>
792 method. You simply have to say C<no Moose> at the bottom of your code for this
793 to work. Here is an example:
798 has 'first_name' => (is => 'rw', isa => 'Str');
799 has 'last_name' => (is => 'rw', isa => 'Str');
803 $self->first_name . ' ' . $self->last_name
806 no Moose; # keywords are removed from the Person package
808 =head1 EXTENDING AND EMBEDDING MOOSE
810 Moose also offers some options for extending or embedding it into your own
811 framework. The basic premise is to have something that sets up your class'
812 metaclass and export the moose declarators (C<has>, C<with>, C<extends>,...).
819 my $CALLER = caller();
824 # we should never export to main
825 return if $CALLER eq 'main';
826 Moose::init_meta( $CALLER, 'MyFramework::Base' );
827 Moose->import({into => $CALLER});
829 # Do my custom framework stuff
836 Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
837 and C<{into_level =E<gt> 1}>
839 =head2 B<init_meta ($class, $baseclass, $metaclass)>
841 Moose does some boot strapping: it creates a metaclass object for your class,
842 and then injects a C<meta> accessor into your class to retrieve it. Then it
843 sets your baseclass to Moose::Object or the value you pass in unless you already
844 have one. This is all done via C<init_meta> which takes the name of your class
845 and optionally a baseclass and a metaclass as arguments.
853 It should be noted that C<super> and C<inner> B<cannot> be used in the same
854 method. However, they may be combined within the same class hierarchy; see
855 F<t/014_override_augment_inner_super.t> for an example.
857 The reason for this is that C<super> is only valid within a method
858 with the C<override> modifier, and C<inner> will never be valid within an
859 C<override> method. In fact, C<augment> will skip over any C<override> methods
860 when searching for its appropriate C<inner>.
862 This might seem like a restriction, but I am of the opinion that keeping these
863 two features separate (yet interoperable) actually makes them easy to use, since
864 their behavior is then easier to predict. Time will tell whether I am right or
865 not (UPDATE: so far so good).
869 It is important to note that we currently have no simple way of combining
870 multiple extended versions of Moose (see L<EXTENDING AND EMBEDDING MOOSE> above),
871 and that in many cases they will conflict with one another. We are working on
872 developing a way around this issue, but in the meantime, you have been warned.
876 =head1 ACKNOWLEDGEMENTS
880 =item I blame Sam Vilain for introducing me to the insanity that is meta-models.
882 =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6.
884 =item Without Yuval "nothingmuch" Kogman this module would not be possible,
885 and it certainly wouldn't have this name ;P
887 =item The basis of the TypeContraints module was Rob Kinyon's idea
888 originally, I just ran with it.
890 =item Thanks to mst & chansen and the whole #moose posse for all the
891 early ideas/feature-requests/encouragement/bug-finding.
893 =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes.
901 =item L<http://www.iinteractive.com/moose>
903 This is the official web home of Moose, it contains links to our public SVN repo
904 as well as links to a number of talks and articles on Moose and Moose related
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 L<MooseX::> namespace.
923 =item The Art of the MetaObject Protocol
925 I mention this in the L<Class::MOP> docs too, this book was critical in
926 the development of both modules and is highly recommended.
934 =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf>
936 This paper (suggested by lbr on #moose) was what lead to the implementation
937 of the C<super>/C<override> and C<inner>/C<augment> features. If you really
938 want to understand them, I suggest you read this.
944 All complex software has bugs lurking in it, and this module is no
945 exception. If you find a bug please either email me, or add the bug
950 Stevan Little E<lt>stevan@iinteractive.comE<gt>
952 B<with contributions from:>
958 Anders (Debolaz) Nor Berle
960 Nathan (kolibre) Gray
962 Christian (chansen) Hansen
964 Hans Dieter (confound) Pearcey
966 Eric (ewilhelm) Wilhelm
968 Guillermo (groditi) Roditi
970 Jess (castaway) Robinson
974 Robert (phaylon) Sedlacek
978 Scott (konobi) McWhirter
980 Shlomi (rindolf) Fish
982 Yuval (nothingmuch) Kogman
984 Chris (perigrin) Prather
986 Jonathan (jrockway) Rockway
988 Piotr (dexter) Roszatycki
994 ... and many other #moose folks
996 =head1 COPYRIGHT AND LICENSE
998 Copyright 2006-2008 by Infinity Interactive, Inc.
1000 L<http://www.iinteractive.com>
1002 This library is free software; you can redistribute it and/or modify
1003 it under the same terms as Perl itself.