8 our $AUTHORITY = 'cpan:STEVAN';
10 use Scalar::Util 'blessed', 'reftype';
11 use Carp 'confess', 'croak', 'cluck';
17 use Moose::Meta::Class;
18 use Moose::Meta::TypeConstraint;
19 use Moose::Meta::TypeCoercion;
20 use Moose::Meta::Attribute;
21 use Moose::Meta::Instance;
23 use Moose::Meta::Role;
26 use Moose::Util::TypeConstraints;
33 my ( $class, $base_class, $metaclass ) = @_;
34 $base_class = 'Moose::Object' unless defined $base_class;
35 $metaclass = 'Moose::Meta::Class' unless defined $metaclass;
38 "The Metaclass $metaclass must be a subclass of Moose::Meta::Class."
39 unless $metaclass->isa('Moose::Meta::Class');
41 # make a subtype for each Moose class
43 unless find_type_constraint($class);
46 if ( $class->can('meta') ) {
48 # this is the case where the metaclass pragma
49 # was used before the 'use Moose' statement to
50 # override a specific class
51 $meta = $class->meta();
52 ( blessed($meta) && $meta->isa('Moose::Meta::Class') )
53 || confess "You already have a &meta function, but it does not return a Moose::Meta::Class";
57 # this is broken currently, we actually need
58 # to allow the possiblity of an inherited
59 # meta, which will not be visible until the
60 # user 'extends' first. This needs to have
61 # more intelligence to it
62 $meta = $metaclass->initialize($class);
65 # re-initialize so it inherits properly
66 $metaclass->initialize( blessed( $_[0] ) || $_[0] );
71 # make sure they inherit from Moose::Object
72 $meta->superclasses($base_class)
73 unless $meta->superclasses();
81 return Class::MOP::subname('Moose::extends' => sub (@) {
82 confess "Must derive at least one class" unless @_;
85 foreach my $super (@supers) {
86 Class::MOP::load_class($super);
89 # this checks the metaclass to make sure
90 # it is correct, sometimes it can get out
91 # of sync when the classes are being built
92 my $meta = $class->meta->_fix_metaclass_incompatability(@supers);
93 $meta->superclasses(@supers);
98 return Class::MOP::subname('Moose::with' => sub (@) {
99 Moose::Util::apply_all_roles($class->meta, @_)
104 return Class::MOP::subname('Moose::has' => sub ($;%) {
106 croak 'Usage: has \'name\' => ( key => value, ... )' if @_ == 1;
108 my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ];
109 $class->meta->add_attribute( $_, %options ) for @$attrs;
114 return Class::MOP::subname('Moose::before' => sub (@&) {
116 my $meta = $class->meta;
117 $meta->add_before_method_modifier( $_, $code ) for @_;
122 return Class::MOP::subname('Moose::after' => sub (@&) {
124 my $meta = $class->meta;
125 $meta->add_after_method_modifier( $_, $code ) for @_;
130 return Class::MOP::subname('Moose::around' => sub (@&) {
132 my $meta = $class->meta;
133 $meta->add_around_method_modifier( $_, $code ) for @_;
137 # FIXME can be made into goto, might break caller() for existing code
138 return Class::MOP::subname('Moose::super' => sub { return unless our $SUPER_BODY; $SUPER_BODY->(our @SUPER_ARGS) })
141 # return subname 'Moose::next' => sub { @_ = our @SUPER_ARGS; goto \&next::method };
145 return Class::MOP::subname('Moose::override' => sub ($&) {
146 my ( $name, $method ) = @_;
147 $class->meta->add_override_method_modifier( $name => $method );
151 return Class::MOP::subname('Moose::inner' => sub {
153 our ( %INNER_BODY, %INNER_ARGS );
155 if ( my $body = $INNER_BODY{$pkg} ) {
156 my @args = @{ $INNER_ARGS{$pkg} };
157 local $INNER_ARGS{$pkg};
158 local $INNER_BODY{$pkg};
159 return $body->(@args);
167 return Class::MOP::subname('Moose::augment' => sub (@&) {
168 my ( $name, $method ) = @_;
169 $class->meta->add_augment_method_modifier( $name => $method );
172 make_immutable => sub {
174 return Class::MOP::subname('Moose::make_immutable' => sub {
175 cluck "The make_immutable keyword has been deprecated, " .
176 "please go back to __PACKAGE__->meta->make_immutable\n";
177 $class->meta->make_immutable(@_);
181 return \&Carp::confess;
184 return \&Scalar::Util::blessed;
188 my $exporter = Sub::Exporter::build_exporter(
190 exports => \%exports,
191 groups => { default => [':all'] }
195 # 1 extra level because it's called by import so there's a layer of indirection
199 ref $_[1] && defined $_[1]->{into}
201 : ref $_[1] && defined $_[1]->{into_level}
202 ? caller($offset + $_[1]->{into_level})
207 $CALLER = _get_caller(@_);
209 # this works because both pragmas set $^H (see perldoc perlvar)
210 # which affects the current compilation - i.e. the file who use'd
211 # us - which is why we don't need to do anything special to make
212 # it affect that file rather than this one (which is already compiled)
217 # we should never export to main
218 return if $CALLER eq 'main';
220 init_meta( $CALLER, 'Moose::Object' );
227 my $class = _get_caller(@_);
229 # loop through the exports ...
230 foreach my $name ( keys %exports ) {
233 if ( defined &{ $class . '::' . $name } ) {
234 my $keyword = \&{ $class . '::' . $name };
236 # make sure it is from Moose
237 my ($pkg_name) = Class::MOP::get_code_info($keyword);
238 next if $pkg_name ne 'Moose';
240 # and if it is from Moose then undef the slot
241 delete ${ $class . '::' }{$name};
248 ## make 'em all immutable
250 $_->meta->make_immutable(
251 inline_constructor => 0,
252 inline_accessors => 1, # these are Class::MOP accessors, so they need inlining
255 'Moose::Meta::Attribute',
256 'Moose::Meta::Class',
257 'Moose::Meta::Instance',
259 'Moose::Meta::TypeConstraint',
260 'Moose::Meta::TypeConstraint::Union',
261 'Moose::Meta::TypeConstraint::Parameterized',
262 'Moose::Meta::TypeCoercion',
264 'Moose::Meta::Method',
265 'Moose::Meta::Method::Accessor',
266 'Moose::Meta::Method::Constructor',
267 'Moose::Meta::Method::Destructor',
268 'Moose::Meta::Method::Overriden',
271 'Moose::Meta::Role::Method',
272 'Moose::Meta::Role::Method::Required',
283 Moose - A postmodern object system for Perl 5
288 use Moose; # automatically turns on strict and warnings
290 has 'x' => (is => 'rw', isa => 'Int');
291 has 'y' => (is => 'rw', isa => 'Int');
304 has 'z' => (is => 'rw', isa => 'Int');
306 after 'clear' => sub {
313 Moose is an extension of the Perl 5 object system.
315 The main goal of Moose is to make Perl 5 Object Oriented programming
316 easier, more consistent and less tedious. With Moose you can to think
317 more about what you want to do and less about the mechanics of OOP.
319 Additionally, Moose is built on top of L<Class::MOP>, which is a
320 metaclass system for Perl 5. This means that Moose not only makes
321 building normal Perl 5 objects better, but it provides the power of
322 metaclass programming as well.
324 =head2 Moose Extensions
326 The L<MooseX::> namespace is the official place to find Moose extensions.
327 There are a number of these modules out on CPAN right now the best way to
328 find them is to search for MooseX:: on search.cpan.org or to look at the
329 latest version of L<Task::Moose> which aims to keep an up to date, easily
330 installable list of these extensions.
332 =head1 BUILDING CLASSES WITH MOOSE
334 Moose makes every attempt to provide as much convenience as possible during
335 class construction/definition, but still stay out of your way if you want it
336 to. Here are a few items to note when building classes with Moose.
338 Unless specified with C<extends>, any class which uses Moose will
339 inherit from L<Moose::Object>.
341 Moose will also manage all attributes (including inherited ones) that are
342 defined with C<has>. And (assuming you call C<new>, which is inherited from
343 L<Moose::Object>) this includes properly initializing all instance slots,
344 setting defaults where appropriate, and performing any type constraint checking
347 =head1 PROVIDED METHODS
349 Moose provides a number of methods to all your classes, mostly through the
350 inheritance of L<Moose::Object>. There is however, one exception.
356 This is a method which provides access to the current class's metaclass.
360 =head1 EXPORTED FUNCTIONS
362 Moose will export a number of functions into the class's namespace which
363 may then be used to set up the class. These functions all work directly
364 on the current class.
368 =item B<extends (@superclasses)>
370 This function will set the superclass(es) for the current class.
372 This approach is recommended instead of C<use base>, because C<use base>
373 actually C<push>es onto the class's C<@ISA>, whereas C<extends> will
374 replace it. This is important to ensure that classes which do not have
375 superclasses still properly inherit from L<Moose::Object>.
377 =item B<with (@roles)>
379 This will apply a given set of C<@roles> to the local class.
381 =item B<has $name =E<gt> %options>
383 This will install an attribute of a given C<$name> into the current class.
384 The C<%options> are the same as those provided by
385 L<Class::MOP::Attribute>, in addition to the list below which are provided
386 by Moose (L<Moose::Meta::Attribute> to be more specific):
390 =item I<is =E<gt> 'rw'|'ro'>
392 The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read
393 only). These will create either a read/write accessor or a read-only
394 accessor respectively, using the same name as the C<$name> of the attribute.
396 If you need more control over how your accessors are named, you can use the
397 I<reader>, I<writer> and I<accessor> options inherited from
398 L<Class::MOP::Attribute>, however if you use those, you won't need the I<is>
401 =item I<isa =E<gt> $type_name>
403 The I<isa> option uses Moose's type constraint facilities to set up runtime
404 type checking for this attribute. Moose will perform the checks during class
405 construction, and within any accessors. The C<$type_name> argument must be a
406 string. The string may be either a class name or a type defined using
407 Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
408 for information on how to define a new type, and how to retrieve type meta-data).
410 =item I<coerce =E<gt> (1|0)>
412 This will attempt to use coercion with the supplied type constraint to change
413 the value passed into any accessors or constructors. You B<must> have supplied
414 a type constraint in order for this to work. See L<Moose::Cookbook::Recipe5>
417 =item I<does =E<gt> $role_name>
419 This will accept the name of a role which the value stored in this attribute
420 is expected to have consumed.
422 =item I<required =E<gt> (1|0)>
424 This marks the attribute as being required. This means a I<defined> value must be
425 supplied during class construction, and the attribute may never be set to
426 C<undef> with an accessor.
428 =item I<weak_ref =E<gt> (1|0)>
430 This will tell the class to store the value of this attribute as a weakened
431 reference. If an attribute is a weakened reference, it B<cannot> also be
434 =item I<lazy =E<gt> (1|0)>
436 This will tell the class to not create this slot until absolutely necessary.
437 If an attribute is marked as lazy it B<must> have a default supplied.
439 =item I<auto_deref =E<gt> (1|0)>
441 This tells the accessor whether to automatically dereference the value returned.
442 This is only legal if your C<isa> option is either C<ArrayRef> or C<HashRef>.
444 =item I<trigger =E<gt> $code>
446 The I<trigger> option is a CODE reference which will be called after the value of
447 the attribute is set. The CODE ref will be passed the instance itself, the
448 updated value and the attribute meta-object (this is for more advanced fiddling
449 and can typically be ignored). You B<cannot> have a trigger on a read-only
452 =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
454 The I<handles> option provides Moose classes with automated delegation features.
455 This is a pretty complex and powerful option. It accepts many different option
456 formats, each with its own benefits and drawbacks.
458 B<NOTE:> The class being delegated to does not need to be a Moose based class,
459 which is why this feature is especially useful when wrapping non-Moose classes.
461 All I<handles> option formats share the following traits:
463 You cannot override a locally defined method with a delegated method; an
464 exception will be thrown if you try. That is to say, if you define C<foo> in
465 your class, you cannot override it with a delegated C<foo>. This is almost never
466 something you would want to do, and if it is, you should do it by hand and not
469 You cannot override any of the methods found in Moose::Object, or the C<BUILD>
470 and C<DEMOLISH> methods. These will not throw an exception, but will silently
471 move on to the next method in the list. My reasoning for this is that you would
472 almost never want to do this, since it usually breaks your class. As with
473 overriding locally defined methods, if you do want to do this, you should do it
474 manually, not with Moose.
476 You do not I<need> to have a reader (or accessor) for the attribute in order
477 to delegate to it. Moose will create a means of accessing the value for you,
478 however this will be several times B<less> efficient then if you had given
479 the attribute a reader (or accessor) to use.
481 Below is the documentation for each option format:
487 This is the most common usage for I<handles>. You basically pass a list of
488 method names to be delegated, and Moose will install a delegation method
493 This is the second most common usage for I<handles>. Instead of a list of
494 method names, you pass a HASH ref where each key is the method name you
495 want installed locally, and its value is the name of the original method
496 in the class being delegated to.
498 This can be very useful for recursive classes like trees. Here is a
499 quick example (soon to be expanded into a Moose::Cookbook::Recipe):
504 has 'node' => (is => 'rw', isa => 'Any');
509 default => sub { [] }
517 parent_node => 'node',
518 siblings => 'children',
522 In this example, the Tree package gets C<parent_node> and C<siblings> methods,
523 which delegate to the C<node> and C<children> methods (respectively) of the Tree
524 instance stored in the C<parent> slot.
528 The regexp option works very similar to the ARRAY option, except that it builds
529 the list of methods for you. It starts by collecting all possible methods of the
530 class being delegated to, then filters that list using the regexp supplied here.
532 B<NOTE:> An I<isa> option is required when using the regexp option format. This
533 is so that we can determine (at compile time) the method list from the class.
534 Without an I<isa> this is just not possible.
538 With the role option, you specify the name of a role whose "interface" then
539 becomes the list of methods to handle. The "interface" can be defined as; the
540 methods of the role and any required methods of the role. It should be noted
541 that this does B<not> include any method modifiers or generated attribute
542 methods (which is consistent with role composition).
546 This is the option to use when you really want to do something funky. You should
547 only use it if you really know what you are doing, as it involves manual
550 This takes a code reference, which should expect two arguments. The first is the
551 attribute meta-object this I<handles> is attached to. The second is the
552 metaclass of the class being delegated to. It expects you to return a hash (not
553 a HASH ref) of the methods you want mapped.
557 =item I<metaclass =E<gt> $metaclass_name>
559 This tells the class to use a custom attribute metaclass for this particular
560 attribute. Custom attribute metaclasses are useful for extending the
561 capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
562 but they are still a fairly advanced topic and too much to cover here, see
563 L<Moose::Cookbook::Recipe11> for more information.
565 The default behavior here is to just load C<$metaclass_name>; however, we also
566 have a way to alias to a shorter name. This will first look to see if
567 B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose
568 will then check to see if that has the method C<register_implementation>, which
569 should return the actual name of the custom attribute metaclass. If there is no
570 C<register_implementation> method, it will fall back to using
571 B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name.
573 =item I<traits =E<gt> [ @role_names ]>
575 This tells Moose to take the list of C<@role_names> and apply them to the
576 attribute meta-object. This is very similar to the I<metaclass> option, but
577 allows you to use more than one extension at a time. This too is an advanced
578 topic, we don't yet have a cookbook for it though.
580 As with I<metaclass>, the default behavior is to just load C<$role_name>; however,
581 we also have a way to alias to a shorter name. This will first look to see if
582 B<Moose::Meta::Attribute::Custom::Trait::$role_name> exists. If it does, Moose
583 will then check to see if that has the method C<register_implementation>, which
584 should return the actual name of the custom attribute trait. If there is no
585 C<register_implementation> method, it will fall back to using
586 B<Moose::Meta::Attribute::Custom::Trait::$metaclass_name> as the trait name.
590 =item B<has +$name =E<gt> %options>
592 This is variation on the normal attibute creator C<has> which allows you to
593 clone and extend an attribute from a superclass or from a role. Here is an
594 example of the superclass usage:
602 default => 'Hello, I am a Foo'
610 has '+message' => (default => 'Hello I am My::Foo');
612 What is happening here is that B<My::Foo> is cloning the C<message> attribute
613 from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt>
614 'Str'> characteristics, but changing the value in C<default>.
616 Here is another example, but within the context of a role:
624 default => 'Hello, I am a Foo'
632 has '+message' => (default => 'Hello I am My::Foo');
634 In this case, we are basically taking the attribute which the role supplied
635 and altering it within the bounds of this feature.
637 Aside from where the attributes come from (one from superclass, the other
638 from a role), this feature works exactly the same. This feature is restricted
639 somewhat, so as to try and force at least I<some> sanity into it. You are only
640 allowed to change the following attributes:
646 Change the default value of an attribute.
650 Change whether the attribute attempts to coerce a value passed to it.
654 Change if the attribute is required to have a value.
656 =item I<documentation>
658 Change the documentation string associated with the attribute.
662 Change if the attribute lazily initializes the slot.
666 You I<are> allowed to change the type without restriction.
668 It is recommended that you use this freedom with caution. We used to
669 only allow for extension only if the type was a subtype of the parent's
670 type, but we felt that was too restrictive and is better left as a
675 You are allowed to B<add> a new C<handles> definition, but you are B<not>
676 allowed to I<change> one.
680 You are allowed to B<add> a new C<builder> definition, but you are B<not>
681 allowed to I<change> one.
685 You are allowed to B<add> a new C<metaclass> definition, but you are
686 B<not> allowed to I<change> one.
690 You are allowed to B<add> additional traits to the C<traits> definition.
691 These traits will be composed into the attribute, but pre-existing traits
692 B<are not> overridden, or removed.
696 =item B<before $name|@names =E<gt> sub { ... }>
698 =item B<after $name|@names =E<gt> sub { ... }>
700 =item B<around $name|@names =E<gt> sub { ... }>
702 This three items are syntactic sugar for the before, after, and around method
703 modifier features that L<Class::MOP> provides. More information on these may be
704 found in the L<Class::MOP::Class documentation|Class::MOP::Class/"Method
709 The keyword C<super> is a no-op when called outside of an C<override> method. In
710 the context of an C<override> method, it will call the next most appropriate
711 superclass method with the same arguments as the original method.
713 =item B<override ($name, &sub)>
715 An C<override> method is a way of explicitly saying "I am overriding this
716 method from my superclass". You can call C<super> within this method, and
717 it will work as expected. The same thing I<can> be accomplished with a normal
718 method call and the C<SUPER::> pseudo-package; it is really your choice.
722 The keyword C<inner>, much like C<super>, is a no-op outside of the context of
723 an C<augment> method. You can think of C<inner> as being the inverse of
724 C<super>; the details of how C<inner> and C<augment> work is best described in
725 the L<Moose::Cookbook::Recipe6>.
727 =item B<augment ($name, &sub)>
729 An C<augment> method, is a way of explicitly saying "I am augmenting this
730 method from my superclass". Once again, the details of how C<inner> and
731 C<augment> work is best described in the L<Moose::Cookbook::Recipe6>.
735 This is the C<Carp::confess> function, and exported here because I use it
740 This is the C<Scalar::Util::blessed> function, it is exported here because I
741 use it all the time. It is highly recommended that this is used instead of
742 C<ref> anywhere you need to test for an object's class name.
746 =head1 UNIMPORTING FUNCTIONS
750 Moose offers a way to remove the keywords it exports, through the C<unimport>
751 method. You simply have to say C<no Moose> at the bottom of your code for this
752 to work. Here is an example:
757 has 'first_name' => (is => 'rw', isa => 'Str');
758 has 'last_name' => (is => 'rw', isa => 'Str');
762 $self->first_name . ' ' . $self->last_name
765 no Moose; # keywords are removed from the Person package
767 =head1 EXTENDING AND EMBEDDING MOOSE
769 Moose also offers some options for extending or embedding it into your own
770 framework. The basic premise is to have something that sets up your class'
771 metaclass and export the moose declarators (C<has>, C<with>, C<extends>,...).
778 my $CALLER = caller();
783 # we should never export to main
784 return if $CALLER eq 'main';
785 Moose::init_meta( $CALLER, 'MyFramework::Base' );
786 Moose->import({into => $CALLER});
788 # Do my custom framework stuff
795 Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
796 and C<{into_level =E<gt> 1}>
798 =head2 B<init_meta ($class, $baseclass, $metaclass)>
800 Moose does some boot strapping: it creates a metaclass object for your class,
801 and then injects a C<meta> accessor into your class to retrieve it. Then it
802 sets your baseclass to Moose::Object or the value you pass in unless you already
803 have one. This is all done via C<init_meta> which takes the name of your class
804 and optionally a baseclass and a metaclass as arguments.
812 It should be noted that C<super> and C<inner> B<cannot> be used in the same
813 method. However, they may be combined within the same class hierarchy; see
814 F<t/014_override_augment_inner_super.t> for an example.
816 The reason for this is that C<super> is only valid within a method
817 with the C<override> modifier, and C<inner> will never be valid within an
818 C<override> method. In fact, C<augment> will skip over any C<override> methods
819 when searching for its appropriate C<inner>.
821 This might seem like a restriction, but I am of the opinion that keeping these
822 two features separate (yet interoperable) actually makes them easy to use, since
823 their behavior is then easier to predict. Time will tell whether I am right or
824 not (UPDATE: so far so good).
828 It is important to note that we currently have no simple way of combining
829 multiple extended versions of Moose (see L<EXTENDING AND EMBEDDING MOOSE> above),
830 and that in many cases they will conflict with one another. We are working on
831 developing a way around this issue, but in the meantime, you have been warned.
837 In case you are still asking yourself "Why do I need this?", then this
838 section is for you. This used to be part of the main DESCRIPTION, but
839 I think Moose no longer actually needs justification, so it is included
840 (read: buried) here for those who are still not convinced.
844 =item Another object system!?!?
846 Yes, I know there has been an explosion recently of new ways to
847 build objects in Perl 5, most of them based on inside-out objects
848 and other such things. Moose is different because it is not a new
849 object system for Perl 5, but instead an extension of the existing
852 Moose is built on top of L<Class::MOP>, which is a metaclass system
853 for Perl 5. This means that Moose not only makes building normal
854 Perl 5 objects better, but it also provides the power of metaclass
857 =item Is this for real? Or is this just an experiment?
859 Moose is I<based> on the prototypes and experiments I did for the Perl 6
860 meta-model. However, Moose is B<NOT> an experiment/prototype; it is for B<real>.
862 =item Is this ready for use in production?
864 Yes, I believe that it is.
866 Moose has been used successfully in production environemnts by several people
867 and companies (including the one I work for). There are Moose applications
868 which have been in production with little or no issue now for well over two years.
869 I consider it highly stable and we are commited to keeping it stable.
871 Of course, in the end, you need to make this call yourself. If you have
872 any questions or concerns, please feel free to email me, or even the list
873 or just stop by #moose and ask away.
875 =item Is Moose just Perl 6 in Perl 5?
877 No. While Moose is very much inspired by Perl 6, it is not itself Perl 6.
878 Instead, it is an OO system for Perl 5. I built Moose because I was tired of
879 writing the same old boring Perl 5 OO code, and drooling over Perl 6 OO. So
880 instead of switching to Ruby, I wrote Moose :)
882 =item Wait, I<post> modern, I thought it was just I<modern>?
884 So I was reading Larry Wall's talk from the 1999 Linux World entitled
885 "Perl, the first postmodern computer language" in which he talks about how
886 he picked the features for Perl because he thought they were cool and he
887 threw out the ones that he thought sucked. This got me thinking about how
888 we have done the same thing in Moose. For Moose, we have "borrowed" features
889 from Perl 6, CLOS (LISP), Smalltalk, Java, BETA, OCaml, Ruby and more, and
890 the bits we didn't like (cause they sucked) we tossed aside. So for this
891 reason (and a few others) I have re-dubbed Moose a I<postmodern> object system.
897 =head1 ACKNOWLEDGEMENTS
901 =item I blame Sam Vilain for introducing me to the insanity that is meta-models.
903 =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6.
905 =item Without Yuval "nothingmuch" Kogman this module would not be possible,
906 and it certainly wouldn't have this name ;P
908 =item The basis of the TypeContraints module was Rob Kinyon's idea
909 originally, I just ran with it.
911 =item Thanks to mst & chansen and the whole #moose posse for all the
912 early ideas/feature-requests/encouragement/bug-finding.
914 =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes.
922 =item L<http://www.iinteractive.com/moose>
924 This is the official web home of Moose, it contains links to our public SVN repo
925 as well as links to a number of talks and articles on Moose and Moose related
928 =item L<Class::MOP> documentation
930 =item The #moose channel on irc.perl.org
932 =item The Moose mailing list - moose@perl.org
934 =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/moose>
936 =item Several Moose extension modules in the L<MooseX::> namespace.
944 =item The Art of the MetaObject Protocol
946 I mention this in the L<Class::MOP> docs too, this book was critical in
947 the development of both modules and is highly recommended.
955 =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf>
957 This paper (suggested by lbr on #moose) was what lead to the implementation
958 of the C<super>/C<override> and C<inner>/C<augment> features. If you really
959 want to understand them, I suggest you read this.
965 All complex software has bugs lurking in it, and this module is no
966 exception. If you find a bug please either email me, or add the bug
971 Stevan Little E<lt>stevan@iinteractive.comE<gt>
973 B<with contributions from:>
979 Anders (Debolaz) Nor Berle
981 Nathan (kolibre) Gray
983 Christian (chansen) Hansen
985 Hans Dieter (confound) Pearcey
987 Eric (ewilhelm) Wilhelm
989 Guillermo (groditi) Roditi
991 Jess (castaway) Robinson
995 Robert (phaylon) Sedlacek
999 Scott (konobi) McWhirter
1001 Shlomi (rindolf) Fish
1003 Yuval (nothingmuch) Kogman
1005 Chris (perigrin) Prather
1007 Jonathan (jrockway) Rockway
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.