8 our $AUTHORITY = 'cpan:STEVAN';
10 use Scalar::Util 'blessed';
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;
35 return Class::MOP::subname('Moose::extends' => sub (@) {
36 croak "Must derive at least one class" unless @_;
39 foreach my $super (@supers) {
40 Class::MOP::load_class($super);
41 croak "You cannot inherit from a Moose Role ($super)"
42 if $super->can('meta') &&
43 blessed $super->meta &&
44 $super->meta->isa('Moose::Meta::Role')
49 # this checks the metaclass to make sure
50 # it is correct, sometimes it can get out
51 # of sync when the classes are being built
52 my $meta = $class->meta->_fix_metaclass_incompatability(@supers);
53 $meta->superclasses(@supers);
58 return Class::MOP::subname('Moose::with' => sub (@) {
59 Moose::Util::apply_all_roles($class->meta, @_)
64 return Class::MOP::subname('Moose::has' => sub ($;%) {
66 croak 'Usage: has \'name\' => ( key => value, ... )' if @_ == 1;
68 my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ];
69 $class->meta->add_attribute( $_, %options ) for @$attrs;
74 return Class::MOP::subname('Moose::before' => sub (@&) {
75 Moose::Util::add_method_modifier($class, 'before', \@_);
80 return Class::MOP::subname('Moose::after' => sub (@&) {
81 Moose::Util::add_method_modifier($class, 'after', \@_);
86 return Class::MOP::subname('Moose::around' => sub (@&) {
87 Moose::Util::add_method_modifier($class, 'around', \@_);
91 return Class::MOP::subname('Moose::super' => sub {
92 return unless our $SUPER_BODY; $SUPER_BODY->(our @SUPER_ARGS)
97 return Class::MOP::subname('Moose::override' => sub ($&) {
98 my ( $name, $method ) = @_;
99 $class->meta->add_override_method_modifier( $name => $method );
103 return Class::MOP::subname('Moose::inner' => sub {
105 our ( %INNER_BODY, %INNER_ARGS );
107 if ( my $body = $INNER_BODY{$pkg} ) {
108 my @args = @{ $INNER_ARGS{$pkg} };
109 local $INNER_ARGS{$pkg};
110 local $INNER_BODY{$pkg};
111 return $body->(@args);
119 return Class::MOP::subname('Moose::augment' => sub (@&) {
120 my ( $name, $method ) = @_;
121 $class->meta->add_augment_method_modifier( $name => $method );
124 make_immutable => sub {
126 return Class::MOP::subname('Moose::make_immutable' => sub {
127 cluck "The make_immutable keyword has been deprecated, " .
128 "please go back to __PACKAGE__->meta->make_immutable\n";
129 $class->meta->make_immutable(@_);
133 return \&Carp::confess;
136 return \&Scalar::Util::blessed;
140 my $exporter = Sub::Exporter::build_exporter(
142 exports => \%exports,
143 groups => { default => [':all'] }
147 # 1 extra level because it's called by import so there's a layer of indirection
151 (ref $_[1] && defined $_[1]->{into})
153 : (ref $_[1] && defined $_[1]->{into_level})
154 ? caller($offset + $_[1]->{into_level})
159 $CALLER = _get_caller(@_);
161 # this works because both pragmas set $^H (see perldoc perlvar)
162 # which affects the current compilation - i.e. the file who use'd
163 # us - which is why we don't need to do anything special to make
164 # it affect that file rather than this one (which is already compiled)
169 # we should never export to main
170 return if $CALLER eq 'main';
172 init_meta( $CALLER, 'Moose::Object' );
178 # This is for special use by
179 # some modules and stuff, I
180 # dont know if it is sane enough
181 # to document actually.
183 sub __CURRY_EXPORTS_FOR_CLASS__ {
186 || croak "_import_into must be called a function, not a method";
187 ($CALLER->can('meta') && $CALLER->meta->isa('Class::MOP::Class'))
188 || croak "Cannot call _import_into on a package ($CALLER) without a metaclass";
189 return map { $_ => $exports{$_}->() } (@_ ? @_ : keys %exports);
194 my $class = _get_caller(@_);
196 # loop through the exports ...
197 foreach my $name ( keys %exports ) {
200 if ( defined &{ $class . '::' . $name } ) {
201 my $keyword = \&{ $class . '::' . $name };
203 # make sure it is from Moose
204 my ($pkg_name) = Class::MOP::get_code_info($keyword);
205 next if $pkg_name ne 'Moose';
207 # and if it is from Moose then undef the slot
208 delete ${ $class . '::' }{$name};
216 my ( $class, $base_class, $metaclass ) = @_;
217 $base_class = 'Moose::Object' unless defined $base_class;
218 $metaclass = 'Moose::Meta::Class' unless defined $metaclass;
221 "The Metaclass $metaclass must be a subclass of Moose::Meta::Class."
222 unless $metaclass->isa('Moose::Meta::Class');
224 # make a subtype for each Moose class
226 unless find_type_constraint($class);
229 if ( $class->can('meta') ) {
231 # this is the case where the metaclass pragma
232 # was used before the 'use Moose' statement to
233 # override a specific class
234 $meta = $class->meta();
235 ( blessed($meta) && $meta->isa('Moose::Meta::Class') )
236 || confess "You already have a &meta function, but it does not return a Moose::Meta::Class";
240 # this is broken currently, we actually need
241 # to allow the possiblity of an inherited
242 # meta, which will not be visible until the
243 # user 'extends' first. This needs to have
244 # more intelligence to it
245 $meta = $metaclass->initialize($class);
248 # re-initialize so it inherits properly
249 $metaclass->initialize( blessed( $_[0] ) || $_[0] );
254 # make sure they inherit from Moose::Object
255 $meta->superclasses($base_class)
256 unless $meta->superclasses();
261 ## make 'em all immutable
263 $_->meta->make_immutable(
264 inline_constructor => 0,
265 inline_accessors => 1, # these are Class::MOP accessors, so they need inlining
268 'Moose::Meta::Attribute',
269 'Moose::Meta::Class',
270 'Moose::Meta::Instance',
272 'Moose::Meta::TypeConstraint',
273 'Moose::Meta::TypeConstraint::Union',
274 'Moose::Meta::TypeConstraint::Parameterized',
275 'Moose::Meta::TypeCoercion',
277 'Moose::Meta::Method',
278 'Moose::Meta::Method::Accessor',
279 'Moose::Meta::Method::Constructor',
280 'Moose::Meta::Method::Destructor',
281 'Moose::Meta::Method::Overriden',
284 'Moose::Meta::Role::Method',
285 'Moose::Meta::Role::Method::Required',
296 Moose - A postmodern object system for Perl 5
301 use Moose; # automatically turns on strict and warnings
303 has 'x' => (is => 'rw', isa => 'Int');
304 has 'y' => (is => 'rw', isa => 'Int');
317 has 'z' => (is => 'rw', isa => 'Int');
319 after 'clear' => sub {
326 Moose is an extension of the Perl 5 object system.
328 The main goal of Moose is to make Perl 5 Object Oriented programming
329 easier, more consistent and less tedious. With Moose you can to think
330 more about what you want to do and less about the mechanics of OOP.
332 Additionally, Moose is built on top of L<Class::MOP>, which is a
333 metaclass system for Perl 5. This means that Moose not only makes
334 building normal Perl 5 objects better, but it provides the power of
335 metaclass programming as well.
337 =head2 Moose Extensions
339 The C<MooseX::> namespace is the official place to find Moose extensions.
340 These extensions can be found on the CPAN. The easiest way to find them
341 is to search for them (L<http://search.cpan.org/search?query=MooseX::>),
342 or to examine L<Task::Moose> which aims to keep an up-to-date, easily
343 installable list of Moose extensions.
345 =head1 BUILDING CLASSES WITH MOOSE
347 Moose makes every attempt to provide as much convenience as possible during
348 class construction/definition, but still stay out of your way if you want it
349 to. Here are a few items to note when building classes with Moose.
351 Unless specified with C<extends>, any class which uses Moose will
352 inherit from L<Moose::Object>.
354 Moose will also manage all attributes (including inherited ones) that are
355 defined with C<has>. And (assuming you call C<new>, which is inherited from
356 L<Moose::Object>) this includes properly initializing all instance slots,
357 setting defaults where appropriate, and performing any type constraint checking
360 =head1 PROVIDED METHODS
362 Moose provides a number of methods to all your classes, mostly through the
363 inheritance of L<Moose::Object>. There is however, one exception.
369 This is a method which provides access to the current class's metaclass.
373 =head1 EXPORTED FUNCTIONS
375 Moose will export a number of functions into the class's namespace which
376 may then be used to set up the class. These functions all work directly
377 on the current class.
381 =item B<extends (@superclasses)>
383 This function will set the superclass(es) for the current class.
385 This approach is recommended instead of C<use base>, because C<use base>
386 actually C<push>es onto the class's C<@ISA>, whereas C<extends> will
387 replace it. This is important to ensure that classes which do not have
388 superclasses still properly inherit from L<Moose::Object>.
390 =item B<with (@roles)>
392 This will apply a given set of C<@roles> to the local class.
394 =item B<has $name =E<gt> %options>
396 This will install an attribute of a given C<$name> into the current class.
397 The C<%options> are the same as those provided by
398 L<Class::MOP::Attribute>, in addition to the list below which are provided
399 by Moose (L<Moose::Meta::Attribute> to be more specific):
403 =item I<is =E<gt> 'rw'|'ro'>
405 The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read
406 only). These will create either a read/write accessor or a read-only
407 accessor respectively, using the same name as the C<$name> of the attribute.
409 If you need more control over how your accessors are named, you can use the
410 I<reader>, I<writer> and I<accessor> options inherited from
411 L<Class::MOP::Attribute>, however if you use those, you won't need the I<is>
414 =item I<isa =E<gt> $type_name>
416 The I<isa> option uses Moose's type constraint facilities to set up runtime
417 type checking for this attribute. Moose will perform the checks during class
418 construction, and within any accessors. The C<$type_name> argument must be a
419 string. The string may be either a class name or a type defined using
420 Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
421 for information on how to define a new type, and how to retrieve type meta-data).
423 =item I<coerce =E<gt> (1|0)>
425 This will attempt to use coercion with the supplied type constraint to change
426 the value passed into any accessors or constructors. You B<must> have supplied
427 a type constraint in order for this to work. See L<Moose::Cookbook::Basics::Recipe5>
430 =item I<does =E<gt> $role_name>
432 This will accept the name of a role which the value stored in this attribute
433 is expected to have consumed.
435 =item I<required =E<gt> (1|0)>
437 This marks the attribute as being required. This means a I<defined> value must be
438 supplied during class construction, and the attribute may never be set to
439 C<undef> with an accessor.
441 =item I<weak_ref =E<gt> (1|0)>
443 This will tell the class to store the value of this attribute as a weakened
444 reference. If an attribute is a weakened reference, it B<cannot> also be
447 =item I<lazy =E<gt> (1|0)>
449 This will tell the class to not create this slot until absolutely necessary.
450 If an attribute is marked as lazy it B<must> have a default supplied.
452 =item I<auto_deref =E<gt> (1|0)>
454 This tells the accessor whether to automatically dereference the value returned.
455 This is only legal if your C<isa> option is either C<ArrayRef> or C<HashRef>.
457 =item I<trigger =E<gt> $code>
459 The I<trigger> option is a CODE reference which will be called after the value of
460 the attribute is set. The CODE ref will be passed the instance itself, the
461 updated value and the attribute meta-object (this is for more advanced fiddling
462 and can typically be ignored). You B<cannot> have a trigger on a read-only
465 =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
467 The I<handles> option provides Moose classes with automated delegation features.
468 This is a pretty complex and powerful option. It accepts many different option
469 formats, each with its own benefits and drawbacks.
471 B<NOTE:> The class being delegated to does not need to be a Moose based class,
472 which is why this feature is especially useful when wrapping non-Moose classes.
474 All I<handles> option formats share the following traits:
476 You cannot override a locally defined method with a delegated method; an
477 exception will be thrown if you try. That is to say, if you define C<foo> in
478 your class, you cannot override it with a delegated C<foo>. This is almost never
479 something you would want to do, and if it is, you should do it by hand and not
482 You cannot override any of the methods found in Moose::Object, or the C<BUILD>
483 and C<DEMOLISH> methods. These will not throw an exception, but will silently
484 move on to the next method in the list. My reasoning for this is that you would
485 almost never want to do this, since it usually breaks your class. As with
486 overriding locally defined methods, if you do want to do this, you should do it
487 manually, not with Moose.
489 You do not I<need> to have a reader (or accessor) for the attribute in order
490 to delegate to it. Moose will create a means of accessing the value for you,
491 however this will be several times B<less> efficient then if you had given
492 the attribute a reader (or accessor) to use.
494 Below is the documentation for each option format:
500 This is the most common usage for I<handles>. You basically pass a list of
501 method names to be delegated, and Moose will install a delegation method
506 This is the second most common usage for I<handles>. Instead of a list of
507 method names, you pass a HASH ref where each key is the method name you
508 want installed locally, and its value is the name of the original method
509 in the class being delegated to.
511 This can be very useful for recursive classes like trees. Here is a
512 quick example (soon to be expanded into a Moose::Cookbook recipe):
517 has 'node' => (is => 'rw', isa => 'Any');
522 default => sub { [] }
530 parent_node => 'node',
531 siblings => 'children',
535 In this example, the Tree package gets C<parent_node> and C<siblings> methods,
536 which delegate to the C<node> and C<children> methods (respectively) of the Tree
537 instance stored in the C<parent> slot.
541 The regexp option works very similar to the ARRAY option, except that it builds
542 the list of methods for you. It starts by collecting all possible methods of the
543 class being delegated to, then filters that list using the regexp supplied here.
545 B<NOTE:> An I<isa> option is required when using the regexp option format. This
546 is so that we can determine (at compile time) the method list from the class.
547 Without an I<isa> this is just not possible.
551 With the role option, you specify the name of a role whose "interface" then
552 becomes the list of methods to handle. The "interface" can be defined as; the
553 methods of the role and any required methods of the role. It should be noted
554 that this does B<not> include any method modifiers or generated attribute
555 methods (which is consistent with role composition).
559 This is the option to use when you really want to do something funky. You should
560 only use it if you really know what you are doing, as it involves manual
563 This takes a code reference, which should expect two arguments. The first is the
564 attribute meta-object this I<handles> is attached to. The second is the
565 metaclass of the class being delegated to. It expects you to return a hash (not
566 a HASH ref) of the methods you want mapped.
570 =item I<metaclass =E<gt> $metaclass_name>
572 This tells the class to use a custom attribute metaclass for this particular
573 attribute. Custom attribute metaclasses are useful for extending the
574 capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
575 but they are still a fairly advanced topic and too much to cover here, see
576 L<Moose::Cookbook::Meta::Recipe1> for more information.
578 The default behavior here is to just load C<$metaclass_name>; however, we also
579 have a way to alias to a shorter name. This will first look to see if
580 B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose
581 will then check to see if that has the method C<register_implementation>, which
582 should return the actual name of the custom attribute metaclass. If there is no
583 C<register_implementation> method, it will fall back to using
584 B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name.
586 =item I<traits =E<gt> [ @role_names ]>
588 This tells Moose to take the list of C<@role_names> and apply them to the
589 attribute meta-object. This is very similar to the I<metaclass> option, but
590 allows you to use more than one extension at a time. This too is an advanced
591 topic, we don't yet have a cookbook for it though.
593 As with I<metaclass>, the default behavior is to just load C<$role_name>; however,
594 we also have a way to alias to a shorter name. This will first look to see if
595 B<Moose::Meta::Attribute::Custom::Trait::$role_name> exists. If it does, Moose
596 will then check to see if that has the method C<register_implementation>, which
597 should return the actual name of the custom attribute trait. If there is no
598 C<register_implementation> method, it will fall back to using
599 B<Moose::Meta::Attribute::Custom::Trait::$metaclass_name> as the trait name.
603 =item B<has +$name =E<gt> %options>
605 This is variation on the normal attibute creator C<has> which allows you to
606 clone and extend an attribute from a superclass or from a role. Here is an
607 example of the superclass usage:
615 default => 'Hello, I am a Foo'
623 has '+message' => (default => 'Hello I am My::Foo');
625 What is happening here is that B<My::Foo> is cloning the C<message> attribute
626 from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt>
627 'Str'> characteristics, but changing the value in C<default>.
629 Here is another example, but within the context of a role:
637 default => 'Hello, I am a Foo'
645 has '+message' => (default => 'Hello I am My::Foo');
647 In this case, we are basically taking the attribute which the role supplied
648 and altering it within the bounds of this feature.
650 Aside from where the attributes come from (one from superclass, the other
651 from a role), this feature works exactly the same. This feature is restricted
652 somewhat, so as to try and force at least I<some> sanity into it. You are only
653 allowed to change the following attributes:
659 Change the default value of an attribute.
663 Change whether the attribute attempts to coerce a value passed to it.
667 Change if the attribute is required to have a value.
669 =item I<documentation>
671 Change the documentation string associated with the attribute.
675 Change if the attribute lazily initializes the slot.
679 You I<are> allowed to change the type without restriction.
681 It is recommended that you use this freedom with caution. We used to
682 only allow for extension only if the type was a subtype of the parent's
683 type, but we felt that was too restrictive and is better left as a
688 You are allowed to B<add> a new C<handles> definition, but you are B<not>
689 allowed to I<change> one.
693 You are allowed to B<add> a new C<builder> definition, but you are B<not>
694 allowed to I<change> one.
698 You are allowed to B<add> a new C<metaclass> definition, but you are
699 B<not> allowed to I<change> one.
703 You are allowed to B<add> additional traits to the C<traits> definition.
704 These traits will be composed into the attribute, but pre-existing traits
705 B<are not> overridden, or removed.
709 =item B<before $name|@names =E<gt> sub { ... }>
711 =item B<after $name|@names =E<gt> sub { ... }>
713 =item B<around $name|@names =E<gt> sub { ... }>
715 This three items are syntactic sugar for the before, after, and around method
716 modifier features that L<Class::MOP> provides. More information on these may be
717 found in the L<Class::MOP::Class documentation|Class::MOP::Class/"Method
722 The keyword C<super> is a no-op when called outside of an C<override> method. In
723 the context of an C<override> method, it will call the next most appropriate
724 superclass method with the same arguments as the original method.
726 =item B<override ($name, &sub)>
728 An C<override> method is a way of explicitly saying "I am overriding this
729 method from my superclass". You can call C<super> within this method, and
730 it will work as expected. The same thing I<can> be accomplished with a normal
731 method call and the C<SUPER::> pseudo-package; it is really your choice.
735 The keyword C<inner>, much like C<super>, is a no-op outside of the context of
736 an C<augment> method. You can think of C<inner> as being the inverse of
737 C<super>; the details of how C<inner> and C<augment> work is best described in
738 the L<Moose::Cookbook::Basics::Recipe6>.
740 =item B<augment ($name, &sub)>
742 An C<augment> method, is a way of explicitly saying "I am augmenting this
743 method from my superclass". Once again, the details of how C<inner> and
744 C<augment> work is best described in the L<Moose::Cookbook::Basics::Recipe6>.
748 This is the C<Carp::confess> function, and exported here because I use it
753 This is the C<Scalar::Util::blessed> function, it is exported here because I
754 use it all the time. It is highly recommended that this is used instead of
755 C<ref> anywhere you need to test for an object's class name.
759 =head1 UNIMPORTING FUNCTIONS
763 Moose offers a way to remove the keywords it exports, through the C<unimport>
764 method. You simply have to say C<no Moose> at the bottom of your code for this
765 to work. Here is an example:
770 has 'first_name' => (is => 'rw', isa => 'Str');
771 has 'last_name' => (is => 'rw', isa => 'Str');
775 $self->first_name . ' ' . $self->last_name
778 no Moose; # keywords are removed from the Person package
780 =head1 EXTENDING AND EMBEDDING MOOSE
782 Moose also offers some options for extending or embedding it into your own
783 framework. The basic premise is to have something that sets up your class'
784 metaclass and export the moose declarators (C<has>, C<with>, C<extends>,...).
791 my $CALLER = caller();
796 # we should never export to main
797 return if $CALLER eq 'main';
798 Moose::init_meta( $CALLER, 'MyFramework::Base' );
799 Moose->import({into => $CALLER});
801 # Do my custom framework stuff
808 Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
809 and C<{into_level =E<gt> 1}>
811 =head2 B<init_meta ($class, $baseclass, $metaclass)>
813 Moose does some boot strapping: it creates a metaclass object for your class,
814 and then injects a C<meta> accessor into your class to retrieve it. Then it
815 sets your baseclass to Moose::Object or the value you pass in unless you already
816 have one. This is all done via C<init_meta> which takes the name of your class
817 and optionally a baseclass and a metaclass as arguments.
819 For more detail on this topic, see L<Moose::Cookbook::Extending::Recipe2>.
827 It should be noted that C<super> and C<inner> B<cannot> be used in the same
828 method. However, they may be combined within the same class hierarchy; see
829 F<t/014_override_augment_inner_super.t> for an example.
831 The reason for this is that C<super> is only valid within a method
832 with the C<override> modifier, and C<inner> will never be valid within an
833 C<override> method. In fact, C<augment> will skip over any C<override> methods
834 when searching for its appropriate C<inner>.
836 This might seem like a restriction, but I am of the opinion that keeping these
837 two features separate (yet interoperable) actually makes them easy to use, since
838 their behavior is then easier to predict. Time will tell whether I am right or
839 not (UPDATE: so far so good).
843 It is important to note that we currently have no simple way of combining
844 multiple extended versions of Moose (see L<EXTENDING AND EMBEDDING MOOSE> above),
845 and that in many cases they will conflict with one another. We are working on
846 developing a way around this issue, but in the meantime, you have been warned.
852 In case you are still asking yourself "Why do I need this?", then this
853 section is for you. This used to be part of the main DESCRIPTION, but
854 I think Moose no longer actually needs justification, so it is included
855 (read: buried) here for those who are still not convinced.
859 =item Another object system!?!?
861 Yes, I know there has been an explosion recently of new ways to
862 build objects in Perl 5, most of them based on inside-out objects
863 and other such things. Moose is different because it is not a new
864 object system for Perl 5, but instead an extension of the existing
867 Moose is built on top of L<Class::MOP>, which is a metaclass system
868 for Perl 5. This means that Moose not only makes building normal
869 Perl 5 objects better, but it also provides the power of metaclass
872 =item Is this for real? Or is this just an experiment?
874 Moose is I<based> on the prototypes and experiments I did for the Perl 6
875 meta-model. However, Moose is B<NOT> an experiment/prototype; it is for B<real>.
877 =item Is this ready for use in production?
879 Yes, I believe that it is.
881 Moose has been used successfully in production environemnts by several people
882 and companies (including the one I work for). There are Moose applications
883 which have been in production with little or no issue now for well over two years.
884 I consider it highly stable and we are commited to keeping it stable.
886 Of course, in the end, you need to make this call yourself. If you have
887 any questions or concerns, please feel free to email me, or even the list
888 or just stop by #moose and ask away.
890 =item Is Moose just Perl 6 in Perl 5?
892 No. While Moose is very much inspired by Perl 6, it is not itself Perl 6.
893 Instead, it is an OO system for Perl 5. I built Moose because I was tired of
894 writing the same old boring Perl 5 OO code, and drooling over Perl 6 OO. So
895 instead of switching to Ruby, I wrote Moose :)
897 =item Wait, I<post> modern, I thought it was just I<modern>?
899 So I was reading Larry Wall's talk from the 1999 Linux World entitled
900 "Perl, the first postmodern computer language" in which he talks about how
901 he picked the features for Perl because he thought they were cool and he
902 threw out the ones that he thought sucked. This got me thinking about how
903 we have done the same thing in Moose. For Moose, we have "borrowed" features
904 from Perl 6, CLOS (LISP), Smalltalk, Java, BETA, OCaml, Ruby and more, and
905 the bits we didn't like (cause they sucked) we tossed aside. So for this
906 reason (and a few others) I have re-dubbed Moose a I<postmodern> object system.
912 =head1 ACKNOWLEDGEMENTS
916 =item I blame Sam Vilain for introducing me to the insanity that is meta-models.
918 =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6.
920 =item Without Yuval "nothingmuch" Kogman this module would not be possible,
921 and it certainly wouldn't have this name ;P
923 =item The basis of the TypeContraints module was Rob Kinyon's idea
924 originally, I just ran with it.
926 =item Thanks to mst & chansen and the whole #moose posse for all the
927 early ideas/feature-requests/encouragement/bug-finding.
929 =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes.
937 =item L<http://www.iinteractive.com/moose>
939 This is the official web home of Moose, it contains links to our public SVN repo
940 as well as links to a number of talks and articles on Moose and Moose related
943 =item L<Moose::Cookbook> - How to cook a Moose
945 =item The Moose is flying, a tutorial by Randal Schwartz
947 Part 1 - L<http://www.stonehenge.com/merlyn/LinuxMag/col94.html>
949 Part 2 - L<http://www.stonehenge.com/merlyn/LinuxMag/col95.html>
951 =item L<Class::MOP> documentation
953 =item The #moose channel on irc.perl.org
955 =item The Moose mailing list - moose@perl.org
957 =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/moose>
959 =item Several Moose extension modules in the C<MooseX::> namespace.
961 See L<http://search.cpan.org/search?query=MooseX::> for extensions.
969 =item The Art of the MetaObject Protocol
971 I mention this in the L<Class::MOP> docs too, this book was critical in
972 the development of both modules and is highly recommended.
980 =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf>
982 This paper (suggested by lbr on #moose) was what lead to the implementation
983 of the C<super>/C<override> and C<inner>/C<augment> features. If you really
984 want to understand them, I suggest you read this.
990 All complex software has bugs lurking in it, and this module is no
991 exception. If you find a bug please either email me, or add the bug
994 =head1 FEATURE REQUESTS
996 We are very strict about what features we add to the Moose core, especially
997 the user-visible features. Instead we have made sure that the underlying
998 meta-system of Moose is as extensible as possible so that you can add your
999 own features easily. That said, occasionally there is a feature needed in the
1000 meta-system to support your planned extension, in which case you should
1001 either email the mailing list or join us on irc at #moose to discuss.
1005 Stevan Little E<lt>stevan@iinteractive.comE<gt>
1007 B<with contributions from:>
1011 Adam (Alias) Kennedy
1013 Anders (Debolaz) Nor Berle
1015 Nathan (kolibre) Gray
1017 Christian (chansen) Hansen
1019 Hans Dieter (confound) Pearcey
1021 Eric (ewilhelm) Wilhelm
1023 Guillermo (groditi) Roditi
1025 Jess (castaway) Robinson
1029 Robert (phaylon) Sedlacek
1033 Scott (konobi) McWhirter
1035 Shlomi (rindolf) Fish
1037 Yuval (nothingmuch) Kogman
1039 Chris (perigrin) Prather
1041 Wallace (wreis) Reis
1043 Jonathan (jrockway) Rockway
1045 Piotr (dexter) Roszatycki
1047 Sam (mugwump) Vilain
1049 Shawn (sartak) Moore
1051 ... and many other #moose folks
1053 =head1 COPYRIGHT AND LICENSE
1055 Copyright 2006-2008 by Infinity Interactive, Inc.
1057 L<http://www.iinteractive.com>
1059 This library is free software; you can redistribute it and/or modify
1060 it under the same terms as Perl itself.