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;
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 croak "Must derive at least one class" unless @_;
85 foreach my $super (@supers) {
86 Class::MOP::load_class($super);
87 croak "You cannot inherit from a Moose Role ($super)"
88 if $super->can('meta') &&
89 blessed $super->meta &&
90 $super->meta->isa('Moose::Meta::Role')
95 # this checks the metaclass to make sure
96 # it is correct, sometimes it can get out
97 # of sync when the classes are being built
98 my $meta = $class->meta->_fix_metaclass_incompatability(@supers);
99 $meta->superclasses(@supers);
104 return Class::MOP::subname('Moose::with' => sub (@) {
105 Moose::Util::apply_all_roles($class->meta, @_)
110 return Class::MOP::subname('Moose::has' => sub ($;%) {
112 croak 'Usage: has \'name\' => ( key => value, ... )' if @_ == 1;
114 my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ];
115 $class->meta->add_attribute( $_, %options ) for @$attrs;
120 return Class::MOP::subname('Moose::before' => sub (@&) {
121 Moose::Util::add_method_modifier($class, 'before', \@_);
126 return Class::MOP::subname('Moose::after' => sub (@&) {
127 Moose::Util::add_method_modifier($class, 'after', \@_);
132 return Class::MOP::subname('Moose::around' => sub (@&) {
133 Moose::Util::add_method_modifier($class, 'around', \@_);
137 return Class::MOP::subname('Moose::super' => sub {
138 return unless our $SUPER_BODY; $SUPER_BODY->(our @SUPER_ARGS)
143 return Class::MOP::subname('Moose::override' => sub ($&) {
144 my ( $name, $method ) = @_;
145 $class->meta->add_override_method_modifier( $name => $method );
149 return Class::MOP::subname('Moose::inner' => sub {
151 our ( %INNER_BODY, %INNER_ARGS );
153 if ( my $body = $INNER_BODY{$pkg} ) {
154 my @args = @{ $INNER_ARGS{$pkg} };
155 local $INNER_ARGS{$pkg};
156 local $INNER_BODY{$pkg};
157 return $body->(@args);
165 return Class::MOP::subname('Moose::augment' => sub (@&) {
166 my ( $name, $method ) = @_;
167 $class->meta->add_augment_method_modifier( $name => $method );
170 make_immutable => sub {
172 return Class::MOP::subname('Moose::make_immutable' => sub {
173 cluck "The make_immutable keyword has been deprecated, " .
174 "please go back to __PACKAGE__->meta->make_immutable\n";
175 $class->meta->make_immutable(@_);
179 return \&Carp::confess;
182 return \&Scalar::Util::blessed;
186 my $exporter = Sub::Exporter::build_exporter(
188 exports => \%exports,
189 groups => { default => [':all'] }
193 # 1 extra level because it's called by import so there's a layer of indirection
197 (ref $_[1] && defined $_[1]->{into})
199 : (ref $_[1] && defined $_[1]->{into_level})
200 ? caller($offset + $_[1]->{into_level})
205 $CALLER = _get_caller(@_);
207 # this works because both pragmas set $^H (see perldoc perlvar)
208 # which affects the current compilation - i.e. the file who use'd
209 # us - which is why we don't need to do anything special to make
210 # it affect that file rather than this one (which is already compiled)
215 # we should never export to main
216 return if $CALLER eq 'main';
218 init_meta( $CALLER, 'Moose::Object' );
224 # This is for special use by
225 # some modules and stuff, I
226 # dont know if it is sane enough
227 # to document actually.
229 sub __CURRY_EXPORTS_FOR_CLASS__ {
232 || croak "_import_into must be called a function, not a method";
233 ($CALLER->can('meta') && $CALLER->meta->isa('Class::MOP::Class'))
234 || croak "Cannot call _import_into on a package ($CALLER) without a metaclass";
235 return map { $_ => $exports{$_}->() } (@_ ? @_ : keys %exports);
240 my $class = _get_caller(@_);
242 # loop through the exports ...
243 foreach my $name ( keys %exports ) {
246 if ( defined &{ $class . '::' . $name } ) {
247 my $keyword = \&{ $class . '::' . $name };
249 # make sure it is from Moose
250 my ($pkg_name) = Class::MOP::get_code_info($keyword);
251 next if $pkg_name ne 'Moose';
253 # and if it is from Moose then undef the slot
254 delete ${ $class . '::' }{$name};
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 L<MooseX::> namespace is the official place to find Moose extensions.
340 There are a number of these modules out on CPAN right now the best way to
341 find them is to search for MooseX:: on search.cpan.org or to look at the
342 latest version of L<Task::Moose> which aims to keep an up to date, easily
343 installable list of these 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::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 or $hash>
459 The I<trigger> option is a CODE reference which will be called after the value
460 of 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
462 fiddling and can typically be ignored). You B<cannot> have a trigger on a
463 read-only attribute. It can optionally be a hashref of before/after/around to
464 CODE refs, in which case after/before behave as in the plain CODE ref case,
465 and around first gets a CODE ref which takes the rest of the args and sets the
468 =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
470 The I<handles> option provides Moose classes with automated delegation features.
471 This is a pretty complex and powerful option. It accepts many different option
472 formats, each with its own benefits and drawbacks.
474 B<NOTE:> The class being delegated to does not need to be a Moose based class,
475 which is why this feature is especially useful when wrapping non-Moose classes.
477 All I<handles> option formats share the following traits:
479 You cannot override a locally defined method with a delegated method; an
480 exception will be thrown if you try. That is to say, if you define C<foo> in
481 your class, you cannot override it with a delegated C<foo>. This is almost never
482 something you would want to do, and if it is, you should do it by hand and not
485 You cannot override any of the methods found in Moose::Object, or the C<BUILD>
486 and C<DEMOLISH> methods. These will not throw an exception, but will silently
487 move on to the next method in the list. My reasoning for this is that you would
488 almost never want to do this, since it usually breaks your class. As with
489 overriding locally defined methods, if you do want to do this, you should do it
490 manually, not with Moose.
492 You do not I<need> to have a reader (or accessor) for the attribute in order
493 to delegate to it. Moose will create a means of accessing the value for you,
494 however this will be several times B<less> efficient then if you had given
495 the attribute a reader (or accessor) to use.
497 Below is the documentation for each option format:
503 This is the most common usage for I<handles>. You basically pass a list of
504 method names to be delegated, and Moose will install a delegation method
509 This is the second most common usage for I<handles>. Instead of a list of
510 method names, you pass a HASH ref where each key is the method name you
511 want installed locally, and its value is the name of the original method
512 in the class being delegated to.
514 This can be very useful for recursive classes like trees. Here is a
515 quick example (soon to be expanded into a Moose::Cookbook::Recipe):
520 has 'node' => (is => 'rw', isa => 'Any');
525 default => sub { [] }
533 parent_node => 'node',
534 siblings => 'children',
538 In this example, the Tree package gets C<parent_node> and C<siblings> methods,
539 which delegate to the C<node> and C<children> methods (respectively) of the Tree
540 instance stored in the C<parent> slot.
544 The regexp option works very similar to the ARRAY option, except that it builds
545 the list of methods for you. It starts by collecting all possible methods of the
546 class being delegated to, then filters that list using the regexp supplied here.
548 B<NOTE:> An I<isa> option is required when using the regexp option format. This
549 is so that we can determine (at compile time) the method list from the class.
550 Without an I<isa> this is just not possible.
554 With the role option, you specify the name of a role whose "interface" then
555 becomes the list of methods to handle. The "interface" can be defined as; the
556 methods of the role and any required methods of the role. It should be noted
557 that this does B<not> include any method modifiers or generated attribute
558 methods (which is consistent with role composition).
562 This is the option to use when you really want to do something funky. You should
563 only use it if you really know what you are doing, as it involves manual
566 This takes a code reference, which should expect two arguments. The first is the
567 attribute meta-object this I<handles> is attached to. The second is the
568 metaclass of the class being delegated to. It expects you to return a hash (not
569 a HASH ref) of the methods you want mapped.
573 =item I<metaclass =E<gt> $metaclass_name>
575 This tells the class to use a custom attribute metaclass for this particular
576 attribute. Custom attribute metaclasses are useful for extending the
577 capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
578 but they are still a fairly advanced topic and too much to cover here, see
579 L<Moose::Cookbook::Recipe11> for more information.
581 The default behavior here is to just load C<$metaclass_name>; however, we also
582 have a way to alias to a shorter name. This will first look to see if
583 B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose
584 will then check to see if that has the method C<register_implementation>, which
585 should return the actual name of the custom attribute metaclass. If there is no
586 C<register_implementation> method, it will fall back to using
587 B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name.
589 =item I<traits =E<gt> [ @role_names ]>
591 This tells Moose to take the list of C<@role_names> and apply them to the
592 attribute meta-object. This is very similar to the I<metaclass> option, but
593 allows you to use more than one extension at a time. This too is an advanced
594 topic, we don't yet have a cookbook for it though.
596 As with I<metaclass>, the default behavior is to just load C<$role_name>; however,
597 we also have a way to alias to a shorter name. This will first look to see if
598 B<Moose::Meta::Attribute::Custom::Trait::$role_name> exists. If it does, Moose
599 will then check to see if that has the method C<register_implementation>, which
600 should return the actual name of the custom attribute trait. If there is no
601 C<register_implementation> method, it will fall back to using
602 B<Moose::Meta::Attribute::Custom::Trait::$metaclass_name> as the trait name.
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::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::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 UNIMPORTING FUNCTIONS
766 Moose offers a way to remove the keywords it exports, through the C<unimport>
767 method. You simply have to say C<no Moose> at the bottom of your code for this
768 to work. Here is an example:
773 has 'first_name' => (is => 'rw', isa => 'Str');
774 has 'last_name' => (is => 'rw', isa => 'Str');
778 $self->first_name . ' ' . $self->last_name
781 no Moose; # keywords are removed from the Person package
783 =head1 EXTENDING AND EMBEDDING MOOSE
785 Moose also offers some options for extending or embedding it into your own
786 framework. The basic premise is to have something that sets up your class'
787 metaclass and export the moose declarators (C<has>, C<with>, C<extends>,...).
794 my $CALLER = caller();
799 # we should never export to main
800 return if $CALLER eq 'main';
801 Moose::init_meta( $CALLER, 'MyFramework::Base' );
802 Moose->import({into => $CALLER});
804 # Do my custom framework stuff
811 Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
812 and C<{into_level =E<gt> 1}>
814 =head2 B<init_meta ($class, $baseclass, $metaclass)>
816 Moose does some boot strapping: it creates a metaclass object for your class,
817 and then injects a C<meta> accessor into your class to retrieve it. Then it
818 sets your baseclass to Moose::Object or the value you pass in unless you already
819 have one. This is all done via C<init_meta> which takes the name of your class
820 and optionally a baseclass and a metaclass as arguments.
828 It should be noted that C<super> and C<inner> B<cannot> be used in the same
829 method. However, they may be combined within the same class hierarchy; see
830 F<t/014_override_augment_inner_super.t> for an example.
832 The reason for this is that C<super> is only valid within a method
833 with the C<override> modifier, and C<inner> will never be valid within an
834 C<override> method. In fact, C<augment> will skip over any C<override> methods
835 when searching for its appropriate C<inner>.
837 This might seem like a restriction, but I am of the opinion that keeping these
838 two features separate (yet interoperable) actually makes them easy to use, since
839 their behavior is then easier to predict. Time will tell whether I am right or
840 not (UPDATE: so far so good).
844 It is important to note that we currently have no simple way of combining
845 multiple extended versions of Moose (see L<EXTENDING AND EMBEDDING MOOSE> above),
846 and that in many cases they will conflict with one another. We are working on
847 developing a way around this issue, but in the meantime, you have been warned.
853 In case you are still asking yourself "Why do I need this?", then this
854 section is for you. This used to be part of the main DESCRIPTION, but
855 I think Moose no longer actually needs justification, so it is included
856 (read: buried) here for those who are still not convinced.
860 =item Another object system!?!?
862 Yes, I know there has been an explosion recently of new ways to
863 build objects in Perl 5, most of them based on inside-out objects
864 and other such things. Moose is different because it is not a new
865 object system for Perl 5, but instead an extension of the existing
868 Moose is built on top of L<Class::MOP>, which is a metaclass system
869 for Perl 5. This means that Moose not only makes building normal
870 Perl 5 objects better, but it also provides the power of metaclass
873 =item Is this for real? Or is this just an experiment?
875 Moose is I<based> on the prototypes and experiments I did for the Perl 6
876 meta-model. However, Moose is B<NOT> an experiment/prototype; it is for B<real>.
878 =item Is this ready for use in production?
880 Yes, I believe that it is.
882 Moose has been used successfully in production environemnts by several people
883 and companies (including the one I work for). There are Moose applications
884 which have been in production with little or no issue now for well over two years.
885 I consider it highly stable and we are commited to keeping it stable.
887 Of course, in the end, you need to make this call yourself. If you have
888 any questions or concerns, please feel free to email me, or even the list
889 or just stop by #moose and ask away.
891 =item Is Moose just Perl 6 in Perl 5?
893 No. While Moose is very much inspired by Perl 6, it is not itself Perl 6.
894 Instead, it is an OO system for Perl 5. I built Moose because I was tired of
895 writing the same old boring Perl 5 OO code, and drooling over Perl 6 OO. So
896 instead of switching to Ruby, I wrote Moose :)
898 =item Wait, I<post> modern, I thought it was just I<modern>?
900 So I was reading Larry Wall's talk from the 1999 Linux World entitled
901 "Perl, the first postmodern computer language" in which he talks about how
902 he picked the features for Perl because he thought they were cool and he
903 threw out the ones that he thought sucked. This got me thinking about how
904 we have done the same thing in Moose. For Moose, we have "borrowed" features
905 from Perl 6, CLOS (LISP), Smalltalk, Java, BETA, OCaml, Ruby and more, and
906 the bits we didn't like (cause they sucked) we tossed aside. So for this
907 reason (and a few others) I have re-dubbed Moose a I<postmodern> object system.
913 =head1 ACKNOWLEDGEMENTS
917 =item I blame Sam Vilain for introducing me to the insanity that is meta-models.
919 =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6.
921 =item Without Yuval "nothingmuch" Kogman this module would not be possible,
922 and it certainly wouldn't have this name ;P
924 =item The basis of the TypeContraints module was Rob Kinyon's idea
925 originally, I just ran with it.
927 =item Thanks to mst & chansen and the whole #moose posse for all the
928 early ideas/feature-requests/encouragement/bug-finding.
930 =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes.
938 =item L<http://www.iinteractive.com/moose>
940 This is the official web home of Moose, it contains links to our public SVN repo
941 as well as links to a number of talks and articles on Moose and Moose related
944 =item L<Class::MOP> documentation
946 =item The #moose channel on irc.perl.org
948 =item The Moose mailing list - moose@perl.org
950 =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/moose>
952 =item Several Moose extension modules in the L<MooseX::> namespace.
960 =item The Art of the MetaObject Protocol
962 I mention this in the L<Class::MOP> docs too, this book was critical in
963 the development of both modules and is highly recommended.
971 =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf>
973 This paper (suggested by lbr on #moose) was what lead to the implementation
974 of the C<super>/C<override> and C<inner>/C<augment> features. If you really
975 want to understand them, I suggest you read this.
981 All complex software has bugs lurking in it, and this module is no
982 exception. If you find a bug please either email me, or add the bug
985 =head1 FEATURE REQUESTS
987 We are very strict about what features we add to the Moose core, especially
988 the user-visible features. Instead we have made sure that the underlying
989 meta-system of Moose is as extensible as possible so that you can add your
990 own features easily. That said, occasionally there is a feature needed in the
991 meta-system to support your planned extension, in which case you should
992 either email the mailing list or join us on irc at #moose to discuss.
996 Stevan Little E<lt>stevan@iinteractive.comE<gt>
998 B<with contributions from:>
1002 Adam (Alias) Kennedy
1004 Anders (Debolaz) Nor Berle
1006 Nathan (kolibre) Gray
1008 Christian (chansen) Hansen
1010 Hans Dieter (confound) Pearcey
1012 Eric (ewilhelm) Wilhelm
1014 Guillermo (groditi) Roditi
1016 Jess (castaway) Robinson
1020 Robert (phaylon) Sedlacek
1024 Scott (konobi) McWhirter
1026 Shlomi (rindolf) Fish
1028 Yuval (nothingmuch) Kogman
1030 Chris (perigrin) Prather
1032 Wallace (wreis) Reis
1034 Jonathan (jrockway) Rockway
1036 Piotr (dexter) Roszatycki
1038 Sam (mugwump) Vilain
1040 Shawn (sartak) Moore
1042 ... and many other #moose folks
1044 =head1 COPYRIGHT AND LICENSE
1046 Copyright 2006-2008 by Infinity Interactive, Inc.
1048 L<http://www.iinteractive.com>
1050 This library is free software; you can redistribute it and/or modify
1051 it under the same terms as Perl itself.