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;
25 use Moose::Meta::Role;
26 use Moose::Meta::Role::Composite;
27 use Moose::Meta::Role::Application;
28 use Moose::Meta::Role::Application::RoleSummation;
29 use Moose::Meta::Role::Application::ToClass;
30 use Moose::Meta::Role::Application::ToRole;
31 use Moose::Meta::Role::Application::ToInstance;
32 use Moose::Meta::Role::Application::ToMetaclassInstance;
34 use Moose::Util::TypeConstraints;
40 croak "Must derive at least one class" unless @_;
43 foreach my $super (@supers) {
44 Class::MOP::load_class($super);
45 croak "You cannot inherit from a Moose Role ($super)"
46 if $super->can('meta') &&
47 blessed $super->meta &&
48 $super->meta->isa('Moose::Meta::Role')
53 # this checks the metaclass to make sure
54 # it is correct, sometimes it can get out
55 # of sync when the classes are being built
56 my $meta = Class::MOP::Class->initialize($class)->_fix_metaclass_incompatability(@supers);
57 $meta->superclasses(@supers);
62 Moose::Util::apply_all_roles(Class::MOP::Class->initialize($class), @_);
68 croak 'Usage: has \'name\' => ( key => value, ... )' if @_ == 1;
70 my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ];
71 Class::MOP::Class->initialize($class)->add_attribute( $_, %options ) for @$attrs;
76 Moose::Util::add_method_modifier($class, 'before', \@_);
81 Moose::Util::add_method_modifier($class, 'after', \@_);
86 Moose::Util::add_method_modifier($class, 'around', \@_);
90 return unless our $SUPER_BODY; $SUPER_BODY->(our @SUPER_ARGS);
95 my ( $name, $method ) = @_;
96 Class::MOP::Class->initialize($class)->add_override_method_modifier( $name => $method );
101 our ( %INNER_BODY, %INNER_ARGS );
103 if ( my $body = $INNER_BODY{$pkg} ) {
104 my @args = @{ $INNER_ARGS{$pkg} };
105 local $INNER_ARGS{$pkg};
106 local $INNER_BODY{$pkg};
107 return $body->(@args);
115 my ( $name, $method ) = @_;
116 Class::MOP::Class->initialize($class)->add_augment_method_modifier( $name => $method );
121 cluck "The make_immutable keyword has been deprecated, " .
122 "please go back to __PACKAGE__->meta->make_immutable\n";
123 Class::MOP::Class->initialize($class)->make_immutable(@_);
126 Moose::Exporter->setup_import_methods(
128 qw( extends with has before after around override augment make_immutable )
133 \&Scalar::Util::blessed,
138 # This used to be called as a function. This hack preserves
139 # backwards compatibility.
140 if ( $_[0] ne __PACKAGE__ ) {
141 return __PACKAGE__->init_meta(
151 my $class = $args{for_class}
152 or confess "Cannot call init_meta without specifying a for_class";
153 my $base_class = $args{base_class} || 'Moose::Object';
154 my $metaclass = $args{metaclass} || 'Moose::Meta::Class';
157 "The Metaclass $metaclass must be a subclass of Moose::Meta::Class."
158 unless $metaclass->isa('Moose::Meta::Class');
160 # make a subtype for each Moose class
162 unless find_type_constraint($class);
165 if ( $class->can('meta') ) {
167 # this is the case where the metaclass pragma
168 # was used before the 'use Moose' statement to
169 # override a specific class
170 $meta = Class::MOP::Class->initialize($class);
171 ( blessed($meta) && $meta->isa('Moose::Meta::Class') )
172 || confess "$class already has a &meta function, but it does not return a Moose::Meta::Class ($meta)";
176 # this is broken currently, we actually need
177 # to allow the possiblity of an inherited
178 # meta, which will not be visible until the
179 # user 'extends' first. This needs to have
180 # more intelligence to it
181 $meta = $metaclass->initialize($class);
184 # re-initialize so it inherits properly
185 $metaclass->initialize( blessed( $_[0] ) || $_[0] );
190 # make sure they inherit from Moose::Object
191 $meta->superclasses($base_class)
192 unless $meta->superclasses();
198 # This may be used in some older MooseX extensions.
200 goto &Moose::Exporter::_get_caller;
203 ## make 'em all immutable
205 $_->meta->make_immutable(
206 inline_constructor => 1,
207 constructor_name => "_new",
208 inline_accessors => 1, # these are Class::MOP accessors, so they need inlining
211 Moose::Meta::Attribute
213 Moose::Meta::Instance
215 Moose::Meta::TypeConstraint
216 Moose::Meta::TypeConstraint::Union
217 Moose::Meta::TypeConstraint::Parameterized
218 Moose::Meta::TypeConstraint::Parameterizable
219 Moose::Meta::TypeConstraint::Enum
220 Moose::Meta::TypeConstraint::Class
221 Moose::Meta::TypeConstraint::Role
222 Moose::Meta::TypeConstraint::Registry
223 Moose::Meta::TypeCoercion
224 Moose::Meta::TypeCoercion::Union
227 Moose::Meta::Method::Accessor
228 Moose::Meta::Method::Constructor
229 Moose::Meta::Method::Destructor
230 Moose::Meta::Method::Overriden
231 Moose::Meta::Method::Augmented
234 Moose::Meta::Role::Method
235 Moose::Meta::Role::Method::Required
237 Moose::Meta::Role::Composite
239 Moose::Meta::Role::Application
240 Moose::Meta::Role::Application::RoleSummation
241 Moose::Meta::Role::Application::ToClass
242 Moose::Meta::Role::Application::ToRole
243 Moose::Meta::Role::Application::ToInstance
244 Moose::Meta::Role::Application::ToMetaclassInstance
255 Moose - A postmodern object system for Perl 5
260 use Moose; # automatically turns on strict and warnings
262 has 'x' => (is => 'rw', isa => 'Int');
263 has 'y' => (is => 'rw', isa => 'Int');
276 has 'z' => (is => 'rw', isa => 'Int');
278 after 'clear' => sub {
285 Moose is an extension of the Perl 5 object system.
287 The main goal of Moose is to make Perl 5 Object Oriented programming
288 easier, more consistent and less tedious. With Moose you can to think
289 more about what you want to do and less about the mechanics of OOP.
291 Additionally, Moose is built on top of L<Class::MOP>, which is a
292 metaclass system for Perl 5. This means that Moose not only makes
293 building normal Perl 5 objects better, but it provides the power of
294 metaclass programming as well.
298 If you're new to Moose, the best place to start is the
299 L<Moose::Cookbook>. The recipes on Moose basics will get you up to
300 speed with many of Moose's features quickly. Once you have an idea of
301 what Moose can do, you can use the API documentation to get more
302 detail on features which interest you.
304 =head2 Moose Extensions
306 The C<MooseX::> namespace is the official place to find Moose extensions.
307 These extensions can be found on the CPAN. The easiest way to find them
308 is to search for them (L<http://search.cpan.org/search?query=MooseX::>),
309 or to examine L<Task::Moose> which aims to keep an up-to-date, easily
310 installable list of Moose extensions.
312 =head1 BUILDING CLASSES WITH MOOSE
314 Moose makes every attempt to provide as much convenience as possible during
315 class construction/definition, but still stay out of your way if you want it
316 to. Here are a few items to note when building classes with Moose.
318 Unless specified with C<extends>, any class which uses Moose will
319 inherit from L<Moose::Object>.
321 Moose will also manage all attributes (including inherited ones) that are
322 defined with C<has>. And (assuming you call C<new>, which is inherited from
323 L<Moose::Object>) this includes properly initializing all instance slots,
324 setting defaults where appropriate, and performing any type constraint checking
327 =head1 PROVIDED METHODS
329 Moose provides a number of methods to all your classes, mostly through the
330 inheritance of L<Moose::Object>. There is however, one exception.
336 This is a method which provides access to the current class's metaclass.
340 =head1 EXPORTED FUNCTIONS
342 Moose will export a number of functions into the class's namespace which
343 may then be used to set up the class. These functions all work directly
344 on the current class.
348 =item B<extends (@superclasses)>
350 This function will set the superclass(es) for the current class.
352 This approach is recommended instead of C<use base>, because C<use base>
353 actually C<push>es onto the class's C<@ISA>, whereas C<extends> will
354 replace it. This is important to ensure that classes which do not have
355 superclasses still properly inherit from L<Moose::Object>.
357 =item B<with (@roles)>
359 This will apply a given set of C<@roles> to the local class.
361 =item B<has $name =E<gt> %options>
363 This will install an attribute of a given C<$name> into the current class.
364 The C<%options> are the same as those provided by
365 L<Class::MOP::Attribute>, in addition to the list below which are provided
366 by Moose (L<Moose::Meta::Attribute> to be more specific):
370 =item I<is =E<gt> 'rw'|'ro'>
372 The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read
373 only). These will create either a read/write accessor or a read-only
374 accessor respectively, using the same name as the C<$name> of the attribute.
376 If you need more control over how your accessors are named, you can use the
377 I<reader>, I<writer> and I<accessor> options inherited from
378 L<Class::MOP::Attribute>, however if you use those, you won't need the I<is>
381 =item I<isa =E<gt> $type_name>
383 The I<isa> option uses Moose's type constraint facilities to set up runtime
384 type checking for this attribute. Moose will perform the checks during class
385 construction, and within any accessors. The C<$type_name> argument must be a
386 string. The string may be either a class name or a type defined using
387 Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
388 for information on how to define a new type, and how to retrieve type meta-data).
390 =item I<coerce =E<gt> (1|0)>
392 This will attempt to use coercion with the supplied type constraint to change
393 the value passed into any accessors or constructors. You B<must> have supplied
394 a type constraint in order for this to work. See L<Moose::Cookbook::Basics::Recipe5>
397 =item I<does =E<gt> $role_name>
399 This will accept the name of a role which the value stored in this attribute
400 is expected to have consumed.
402 =item I<required =E<gt> (1|0)>
404 This marks the attribute as being required. This means a I<defined> value must be
405 supplied during class construction, and the attribute may never be set to
406 C<undef> with an accessor.
408 =item I<weak_ref =E<gt> (1|0)>
410 This will tell the class to store the value of this attribute as a weakened
411 reference. If an attribute is a weakened reference, it B<cannot> also be
414 =item I<lazy =E<gt> (1|0)>
416 This will tell the class to not create this slot until absolutely necessary.
417 If an attribute is marked as lazy it B<must> have a default supplied.
419 =item I<auto_deref =E<gt> (1|0)>
421 This tells the accessor whether to automatically dereference the value returned.
422 This is only legal if your C<isa> option is either C<ArrayRef> or C<HashRef>.
424 =item I<trigger =E<gt> $code>
426 The I<trigger> option is a CODE reference which will be called after the value of
427 the attribute is set. The CODE ref will be passed the instance itself, the
428 updated value and the attribute meta-object (this is for more advanced fiddling
429 and can typically be ignored). You B<cannot> have a trigger on a read-only
432 =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
434 The I<handles> option provides Moose classes with automated delegation features.
435 This is a pretty complex and powerful option. It accepts many different option
436 formats, each with its own benefits and drawbacks.
438 B<NOTE:> The class being delegated to does not need to be a Moose based class,
439 which is why this feature is especially useful when wrapping non-Moose classes.
441 All I<handles> option formats share the following traits:
443 You cannot override a locally defined method with a delegated method; an
444 exception will be thrown if you try. That is to say, if you define C<foo> in
445 your class, you cannot override it with a delegated C<foo>. This is almost never
446 something you would want to do, and if it is, you should do it by hand and not
449 You cannot override any of the methods found in Moose::Object, or the C<BUILD>
450 and C<DEMOLISH> methods. These will not throw an exception, but will silently
451 move on to the next method in the list. My reasoning for this is that you would
452 almost never want to do this, since it usually breaks your class. As with
453 overriding locally defined methods, if you do want to do this, you should do it
454 manually, not with Moose.
456 You do not I<need> to have a reader (or accessor) for the attribute in order
457 to delegate to it. Moose will create a means of accessing the value for you,
458 however this will be several times B<less> efficient then if you had given
459 the attribute a reader (or accessor) to use.
461 Below is the documentation for each option format:
467 This is the most common usage for I<handles>. You basically pass a list of
468 method names to be delegated, and Moose will install a delegation method
473 This is the second most common usage for I<handles>. Instead of a list of
474 method names, you pass a HASH ref where each key is the method name you
475 want installed locally, and its value is the name of the original method
476 in the class being delegated to.
478 This can be very useful for recursive classes like trees. Here is a
479 quick example (soon to be expanded into a Moose::Cookbook recipe):
484 has 'node' => (is => 'rw', isa => 'Any');
489 default => sub { [] }
497 parent_node => 'node',
498 siblings => 'children',
502 In this example, the Tree package gets C<parent_node> and C<siblings> methods,
503 which delegate to the C<node> and C<children> methods (respectively) of the Tree
504 instance stored in the C<parent> slot.
508 The regexp option works very similar to the ARRAY option, except that it builds
509 the list of methods for you. It starts by collecting all possible methods of the
510 class being delegated to, then filters that list using the regexp supplied here.
512 B<NOTE:> An I<isa> option is required when using the regexp option format. This
513 is so that we can determine (at compile time) the method list from the class.
514 Without an I<isa> this is just not possible.
518 With the role option, you specify the name of a role whose "interface" then
519 becomes the list of methods to handle. The "interface" can be defined as; the
520 methods of the role and any required methods of the role. It should be noted
521 that this does B<not> include any method modifiers or generated attribute
522 methods (which is consistent with role composition).
526 This is the option to use when you really want to do something funky. You should
527 only use it if you really know what you are doing, as it involves manual
530 This takes a code reference, which should expect two arguments. The first is the
531 attribute meta-object this I<handles> is attached to. The second is the
532 metaclass of the class being delegated to. It expects you to return a hash (not
533 a HASH ref) of the methods you want mapped.
537 =item I<metaclass =E<gt> $metaclass_name>
539 This tells the class to use a custom attribute metaclass for this particular
540 attribute. Custom attribute metaclasses are useful for extending the
541 capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
542 but they are still a fairly advanced topic and too much to cover here, see
543 L<Moose::Cookbook::Meta::Recipe1> for more information.
545 The default behavior here is to just load C<$metaclass_name>; however, we also
546 have a way to alias to a shorter name. This will first look to see if
547 B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose
548 will then check to see if that has the method C<register_implementation>, which
549 should return the actual name of the custom attribute metaclass. If there is no
550 C<register_implementation> method, it will fall back to using
551 B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name.
553 =item I<traits =E<gt> [ @role_names ]>
555 This tells Moose to take the list of C<@role_names> and apply them to the
556 attribute meta-object. This is very similar to the I<metaclass> option, but
557 allows you to use more than one extension at a time.
559 See L<TRAIT NAME RESOLUTION> for details on how a trait name is
560 resolved to a class name.
562 Also see L<Moose::Cookbook::Meta::Recipe3> for a metaclass trait
567 =item B<has +$name =E<gt> %options>
569 This is variation on the normal attibute creator C<has> which allows you to
570 clone and extend an attribute from a superclass or from a role. Here is an
571 example of the superclass usage:
579 default => 'Hello, I am a Foo'
587 has '+message' => (default => 'Hello I am My::Foo');
589 What is happening here is that B<My::Foo> is cloning the C<message> attribute
590 from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt>
591 'Str'> characteristics, but changing the value in C<default>.
593 Here is another example, but within the context of a role:
601 default => 'Hello, I am a Foo'
609 has '+message' => (default => 'Hello I am My::Foo');
611 In this case, we are basically taking the attribute which the role supplied
612 and altering it within the bounds of this feature.
614 Aside from where the attributes come from (one from superclass, the other
615 from a role), this feature works exactly the same. This feature is restricted
616 somewhat, so as to try and force at least I<some> sanity into it. You are only
617 allowed to change the following attributes:
623 Change the default value of an attribute.
627 Change whether the attribute attempts to coerce a value passed to it.
631 Change if the attribute is required to have a value.
633 =item I<documentation>
635 Change the documentation string associated with the attribute.
639 Change if the attribute lazily initializes the slot.
643 You I<are> allowed to change the type without restriction.
645 It is recommended that you use this freedom with caution. We used to
646 only allow for extension only if the type was a subtype of the parent's
647 type, but we felt that was too restrictive and is better left as a
652 You are allowed to B<add> a new C<handles> definition, but you are B<not>
653 allowed to I<change> one.
657 You are allowed to B<add> a new C<builder> definition, but you are B<not>
658 allowed to I<change> one.
662 You are allowed to B<add> a new C<metaclass> definition, but you are
663 B<not> allowed to I<change> one.
667 You are allowed to B<add> additional traits to the C<traits> definition.
668 These traits will be composed into the attribute, but pre-existing traits
669 B<are not> overridden, or removed.
673 =item B<before $name|@names =E<gt> sub { ... }>
675 =item B<after $name|@names =E<gt> sub { ... }>
677 =item B<around $name|@names =E<gt> sub { ... }>
679 This three items are syntactic sugar for the before, after, and around method
680 modifier features that L<Class::MOP> provides. More information on these may be
681 found in the L<Class::MOP::Class documentation|Class::MOP::Class/"Method
686 The keyword C<super> is a no-op when called outside of an C<override> method. In
687 the context of an C<override> method, it will call the next most appropriate
688 superclass method with the same arguments as the original method.
690 =item B<override ($name, &sub)>
692 An C<override> method is a way of explicitly saying "I am overriding this
693 method from my superclass". You can call C<super> within this method, and
694 it will work as expected. The same thing I<can> be accomplished with a normal
695 method call and the C<SUPER::> pseudo-package; it is really your choice.
699 The keyword C<inner>, much like C<super>, is a no-op outside of the context of
700 an C<augment> method. You can think of C<inner> as being the inverse of
701 C<super>; the details of how C<inner> and C<augment> work is best described in
702 the L<Moose::Cookbook::Basics::Recipe6>.
704 =item B<augment ($name, &sub)>
706 An C<augment> method, is a way of explicitly saying "I am augmenting this
707 method from my superclass". Once again, the details of how C<inner> and
708 C<augment> work is best described in the L<Moose::Cookbook::Basics::Recipe6>.
712 This is the C<Carp::confess> function, and exported here because I use it
717 This is the C<Scalar::Util::blessed> function, it is exported here because I
718 use it all the time. It is highly recommended that this is used instead of
719 C<ref> anywhere you need to test for an object's class name.
723 =head1 METACLASS TRAITS
725 When you use Moose, you can also specify traits which will be applied
728 use Moose -traits => 'My::Trait';
730 This is very similar to the attribute traits feature. When you do
731 this, your class's C<meta> object will have the specified traits
732 applied to it. See L<TRAIT NAME RESOLUTION> for more details.
734 =head1 TRAIT NAME RESOLUTION
736 By default, when given a trait name, Moose simply tries to load a
737 class of the same name. If such a class does not exist, it then looks
738 for for a class matching
739 B<Moose::Meta::$type::Custom::Trait::$trait_name>. The C<$type>
740 variable here will be one of B<Attribute> or B<Class>, depending on
741 what the trait is being applied to.
743 If a class with this long name exists, Moose checks to see if it has
744 the method C<register_implementation>. This method is expected to
745 return the I<real> class name of the trait. If there is no
746 C<register_implementation> method, it will fall back to using
747 B<Moose::Meta::$type::Custom::Trait::$trait> as the trait name.
749 If all this is confusing, take a look at
750 L<Moose::Cookbook::Meta::Recipe3>, which demonstrates how to create an
753 =head1 UNIMPORTING FUNCTIONS
757 Moose offers a way to remove the keywords it exports, through the C<unimport>
758 method. You simply have to say C<no Moose> at the bottom of your code for this
759 to work. Here is an example:
764 has 'first_name' => (is => 'rw', isa => 'Str');
765 has 'last_name' => (is => 'rw', isa => 'Str');
769 $self->first_name . ' ' . $self->last_name
772 no Moose; # keywords are removed from the Person package
774 =head1 EXTENDING AND EMBEDDING MOOSE
776 Moose also offers some options for extending or embedding it into your
777 own framework. There are several things you might want to do as part
778 of such a framework. First, you probably want to export Moose's sugar
779 functions (C<has>, C<extends>, etc) for users of the
780 framework. Second, you may want to provide additional sugar of your
781 own. Third, you may want to provide your own object base class instead
782 of L<Moose::Object>, and/or your own metaclass class instead of
783 L<Moose::Meta::Class>.
785 The exporting needs can be asily satisfied by using
786 L<Moose::Exporter>, which is what C<Moose.pm> itself uses for
787 exporting. L<Moose::Exporter> lets you "export like Moose".
789 If you define an C<init_meta> method in a module that uses
790 L<Moose::Exporter>, then this method will be called I<before>
791 C<Moose.pm>'s own C<init_meta>. This gives you a chance to provide an
792 alternate object base class or metaclass class.
794 Here is a simple example:
801 use Moose (); # no need to get Moose's exports
804 Moose::Exporter->setup_import_methods( also => 'Moose' );
808 return Moose->init_meta( @_, base_class => 'MyFramework::Base' );
811 In this example, any class that includes C<use MyFramework> will get
812 all of C<Moose.pm>'s sugar functions, and will have their superclass
813 set to C<MyFramework::Base>.
815 Additionally, that class can include C<no MyFramework> to unimport
817 =head2 B<< Moose->init_meta(for_class => $class, base_class => $baseclass, metaclass => $metaclass) >>
819 The C<init_meta> method sets up the metaclass object for the class
820 specified by C<for_class>. This method injects a a C<meta> accessor
821 into the class so you can get at this object. It also sets the class's
822 superclass to C<base_class>, with L<Moose::Object> as the default.
824 You can specify an alternate metaclass with the C<metaclass> parameter.
826 For more detail on this topic, see L<Moose::Cookbook::Extending::Recipe2>.
828 This method used to be documented as a function which accepted
829 positional parameters. This calling style will still work for
830 backwards compatibility, but is deprecated.
834 Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
835 and C<{into_level =E<gt> 1}>.
837 B<NOTE>: Doing this is more or less deprecated. Use L<Moose::Exporter>
838 instead, which lets you stack multiple C<Moose.pm>-alike modules
839 sanely. It handles getting the exported functions into the right place
848 It should be noted that C<super> and C<inner> B<cannot> be used in the same
849 method. However, they may be combined within the same class hierarchy; see
850 F<t/014_override_augment_inner_super.t> for an example.
852 The reason for this is that C<super> is only valid within a method
853 with the C<override> modifier, and C<inner> will never be valid within an
854 C<override> method. In fact, C<augment> will skip over any C<override> methods
855 when searching for its appropriate C<inner>.
857 This might seem like a restriction, but I am of the opinion that keeping these
858 two features separate (yet interoperable) actually makes them easy to use, since
859 their behavior is then easier to predict. Time will tell whether I am right or
860 not (UPDATE: so far so good).
864 It is important to note that we currently have no simple way of combining
865 multiple extended versions of Moose (see L<EXTENDING AND EMBEDDING MOOSE> above),
866 and that in many cases they will conflict with one another. We are working on
867 developing a way around this issue, but in the meantime, you have been warned.
873 In case you are still asking yourself "Why do I need this?", then this
874 section is for you. This used to be part of the main DESCRIPTION, but
875 I think Moose no longer actually needs justification, so it is included
876 (read: buried) here for those who are still not convinced.
880 =item Another object system!?!?
882 Yes, I know there has been an explosion recently of new ways to
883 build objects in Perl 5, most of them based on inside-out objects
884 and other such things. Moose is different because it is not a new
885 object system for Perl 5, but instead an extension of the existing
888 Moose is built on top of L<Class::MOP>, which is a metaclass system
889 for Perl 5. This means that Moose not only makes building normal
890 Perl 5 objects better, but it also provides the power of metaclass
893 =item Is this for real? Or is this just an experiment?
895 Moose is I<based> on the prototypes and experiments I did for the Perl 6
896 meta-model. However, Moose is B<NOT> an experiment/prototype; it is for B<real>.
898 =item Is this ready for use in production?
900 Yes, I believe that it is.
902 Moose has been used successfully in production environemnts by several people
903 and companies (including the one I work for). There are Moose applications
904 which have been in production with little or no issue now for well over two years.
905 I consider it highly stable and we are commited to keeping it stable.
907 Of course, in the end, you need to make this call yourself. If you have
908 any questions or concerns, please feel free to email me, or even the list
909 or just stop by #moose and ask away.
911 =item Is Moose just Perl 6 in Perl 5?
913 No. While Moose is very much inspired by Perl 6, it is not itself Perl 6.
914 Instead, it is an OO system for Perl 5. I built Moose because I was tired of
915 writing the same old boring Perl 5 OO code, and drooling over Perl 6 OO. So
916 instead of switching to Ruby, I wrote Moose :)
918 =item Wait, I<post> modern, I thought it was just I<modern>?
920 So I was reading Larry Wall's talk from the 1999 Linux World entitled
921 "Perl, the first postmodern computer language" in which he talks about how
922 he picked the features for Perl because he thought they were cool and he
923 threw out the ones that he thought sucked. This got me thinking about how
924 we have done the same thing in Moose. For Moose, we have "borrowed" features
925 from Perl 6, CLOS (LISP), Smalltalk, Java, BETA, OCaml, Ruby and more, and
926 the bits we didn't like (cause they sucked) we tossed aside. So for this
927 reason (and a few others) I have re-dubbed Moose a I<postmodern> object system.
933 =head1 ACKNOWLEDGEMENTS
937 =item I blame Sam Vilain for introducing me to the insanity that is meta-models.
939 =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6.
941 =item Without Yuval "nothingmuch" Kogman this module would not be possible,
942 and it certainly wouldn't have this name ;P
944 =item The basis of the TypeContraints module was Rob Kinyon's idea
945 originally, I just ran with it.
947 =item Thanks to mst & chansen and the whole #moose posse for all the
948 early ideas/feature-requests/encouragement/bug-finding.
950 =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes.
958 =item L<http://www.iinteractive.com/moose>
960 This is the official web home of Moose, it contains links to our public SVN repo
961 as well as links to a number of talks and articles on Moose and Moose related
964 =item L<Moose::Cookbook> - How to cook a Moose
966 =item The Moose is flying, a tutorial by Randal Schwartz
968 Part 1 - L<http://www.stonehenge.com/merlyn/LinuxMag/col94.html>
970 Part 2 - L<http://www.stonehenge.com/merlyn/LinuxMag/col95.html>
972 =item L<Class::MOP> documentation
974 =item The #moose channel on irc.perl.org
976 =item The Moose mailing list - moose@perl.org
978 =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/moose>
980 =item Several Moose extension modules in the C<MooseX::> namespace.
982 See L<http://search.cpan.org/search?query=MooseX::> for extensions.
990 =item The Art of the MetaObject Protocol
992 I mention this in the L<Class::MOP> docs too, this book was critical in
993 the development of both modules and is highly recommended.
1001 =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf>
1003 This paper (suggested by lbr on #moose) was what lead to the implementation
1004 of the C<super>/C<override> and C<inner>/C<augment> features. If you really
1005 want to understand them, I suggest you read this.
1011 All complex software has bugs lurking in it, and this module is no
1012 exception. If you find a bug please either email me, or add the bug
1015 =head1 FEATURE REQUESTS
1017 We are very strict about what features we add to the Moose core, especially
1018 the user-visible features. Instead we have made sure that the underlying
1019 meta-system of Moose is as extensible as possible so that you can add your
1020 own features easily. That said, occasionally there is a feature needed in the
1021 meta-system to support your planned extension, in which case you should
1022 either email the mailing list or join us on irc at #moose to discuss.
1026 Stevan Little E<lt>stevan@iinteractive.comE<gt>
1028 B<with contributions from:>
1032 Adam (Alias) Kennedy
1034 Anders (Debolaz) Nor Berle
1036 Nathan (kolibre) Gray
1038 Christian (chansen) Hansen
1040 Hans Dieter (confound) Pearcey
1042 Eric (ewilhelm) Wilhelm
1044 Guillermo (groditi) Roditi
1046 Jess (castaway) Robinson
1050 Robert (phaylon) Sedlacek
1054 Scott (konobi) McWhirter
1056 Shlomi (rindolf) Fish
1058 Yuval (nothingmuch) Kogman
1060 Chris (perigrin) Prather
1062 Wallace (wreis) Reis
1064 Jonathan (jrockway) Rockway
1066 Piotr (dexter) Roszatycki
1068 Sam (mugwump) Vilain
1070 Shawn (sartak) Moore
1072 ... and many other #moose folks
1074 =head1 COPYRIGHT AND LICENSE
1076 Copyright 2006-2008 by Infinity Interactive, Inc.
1078 L<http://www.iinteractive.com>
1080 This library is free software; you can redistribute it and/or modify
1081 it under the same terms as Perl itself.