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 "You already have a &meta function, but it does not return a Moose::Meta::Class";
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::Enum
219 Moose::Meta::TypeConstraint::Class
220 Moose::Meta::TypeConstraint::Role
221 Moose::Meta::TypeConstraint::Registry
222 Moose::Meta::TypeCoercion
223 Moose::Meta::TypeCoercion::Union
226 Moose::Meta::Method::Accessor
227 Moose::Meta::Method::Constructor
228 Moose::Meta::Method::Destructor
229 Moose::Meta::Method::Overriden
230 Moose::Meta::Method::Augmented
233 Moose::Meta::Role::Method
234 Moose::Meta::Role::Method::Required
236 Moose::Meta::Role::Composite
238 Moose::Meta::Role::Application
239 Moose::Meta::Role::Application::RoleSummation
240 Moose::Meta::Role::Application::ToClass
241 Moose::Meta::Role::Application::ToRole
242 Moose::Meta::Role::Application::ToInstance
243 Moose::Meta::Role::Application::ToMetaclassInstance
254 Moose - A postmodern object system for Perl 5
259 use Moose; # automatically turns on strict and warnings
261 has 'x' => (is => 'rw', isa => 'Int');
262 has 'y' => (is => 'rw', isa => 'Int');
275 has 'z' => (is => 'rw', isa => 'Int');
277 after 'clear' => sub {
284 Moose is an extension of the Perl 5 object system.
286 The main goal of Moose is to make Perl 5 Object Oriented programming
287 easier, more consistent and less tedious. With Moose you can to think
288 more about what you want to do and less about the mechanics of OOP.
290 Additionally, Moose is built on top of L<Class::MOP>, which is a
291 metaclass system for Perl 5. This means that Moose not only makes
292 building normal Perl 5 objects better, but it provides the power of
293 metaclass programming as well.
297 If you're new to Moose, the best place to start is the
298 L<Moose::Cookbook>. The recipes on Moose basics will get you up to
299 speed with many of Moose's features quickly. Once you have an idea of
300 what Moose can do, you can use the API documentation to get more
301 detail on features which interest you.
303 =head2 Moose Extensions
305 The C<MooseX::> namespace is the official place to find Moose extensions.
306 These extensions can be found on the CPAN. The easiest way to find them
307 is to search for them (L<http://search.cpan.org/search?query=MooseX::>),
308 or to examine L<Task::Moose> which aims to keep an up-to-date, easily
309 installable list of Moose extensions.
311 =head1 BUILDING CLASSES WITH MOOSE
313 Moose makes every attempt to provide as much convenience as possible during
314 class construction/definition, but still stay out of your way if you want it
315 to. Here are a few items to note when building classes with Moose.
317 Unless specified with C<extends>, any class which uses Moose will
318 inherit from L<Moose::Object>.
320 Moose will also manage all attributes (including inherited ones) that are
321 defined with C<has>. And (assuming you call C<new>, which is inherited from
322 L<Moose::Object>) this includes properly initializing all instance slots,
323 setting defaults where appropriate, and performing any type constraint checking
326 =head1 PROVIDED METHODS
328 Moose provides a number of methods to all your classes, mostly through the
329 inheritance of L<Moose::Object>. There is however, one exception.
335 This is a method which provides access to the current class's metaclass.
339 =head1 EXPORTED FUNCTIONS
341 Moose will export a number of functions into the class's namespace which
342 may then be used to set up the class. These functions all work directly
343 on the current class.
347 =item B<extends (@superclasses)>
349 This function will set the superclass(es) for the current class.
351 This approach is recommended instead of C<use base>, because C<use base>
352 actually C<push>es onto the class's C<@ISA>, whereas C<extends> will
353 replace it. This is important to ensure that classes which do not have
354 superclasses still properly inherit from L<Moose::Object>.
356 =item B<with (@roles)>
358 This will apply a given set of C<@roles> to the local class.
360 =item B<has $name =E<gt> %options>
362 This will install an attribute of a given C<$name> into the current class.
363 The C<%options> are the same as those provided by
364 L<Class::MOP::Attribute>, in addition to the list below which are provided
365 by Moose (L<Moose::Meta::Attribute> to be more specific):
369 =item I<is =E<gt> 'rw'|'ro'>
371 The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read
372 only). These will create either a read/write accessor or a read-only
373 accessor respectively, using the same name as the C<$name> of the attribute.
375 If you need more control over how your accessors are named, you can use the
376 I<reader>, I<writer> and I<accessor> options inherited from
377 L<Class::MOP::Attribute>, however if you use those, you won't need the I<is>
380 =item I<isa =E<gt> $type_name>
382 The I<isa> option uses Moose's type constraint facilities to set up runtime
383 type checking for this attribute. Moose will perform the checks during class
384 construction, and within any accessors. The C<$type_name> argument must be a
385 string. The string may be either a class name or a type defined using
386 Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
387 for information on how to define a new type, and how to retrieve type meta-data).
389 =item I<coerce =E<gt> (1|0)>
391 This will attempt to use coercion with the supplied type constraint to change
392 the value passed into any accessors or constructors. You B<must> have supplied
393 a type constraint in order for this to work. See L<Moose::Cookbook::Basics::Recipe5>
396 =item I<does =E<gt> $role_name>
398 This will accept the name of a role which the value stored in this attribute
399 is expected to have consumed.
401 =item I<required =E<gt> (1|0)>
403 This marks the attribute as being required. This means a I<defined> value must be
404 supplied during class construction, and the attribute may never be set to
405 C<undef> with an accessor.
407 =item I<weak_ref =E<gt> (1|0)>
409 This will tell the class to store the value of this attribute as a weakened
410 reference. If an attribute is a weakened reference, it B<cannot> also be
413 =item I<lazy =E<gt> (1|0)>
415 This will tell the class to not create this slot until absolutely necessary.
416 If an attribute is marked as lazy it B<must> have a default supplied.
418 =item I<auto_deref =E<gt> (1|0)>
420 This tells the accessor whether to automatically dereference the value returned.
421 This is only legal if your C<isa> option is either C<ArrayRef> or C<HashRef>.
423 =item I<trigger =E<gt> $code>
425 The I<trigger> option is a CODE reference which will be called after the value of
426 the attribute is set. The CODE ref will be passed the instance itself, the
427 updated value and the attribute meta-object (this is for more advanced fiddling
428 and can typically be ignored). You B<cannot> have a trigger on a read-only
431 =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
433 The I<handles> option provides Moose classes with automated delegation features.
434 This is a pretty complex and powerful option. It accepts many different option
435 formats, each with its own benefits and drawbacks.
437 B<NOTE:> The class being delegated to does not need to be a Moose based class,
438 which is why this feature is especially useful when wrapping non-Moose classes.
440 All I<handles> option formats share the following traits:
442 You cannot override a locally defined method with a delegated method; an
443 exception will be thrown if you try. That is to say, if you define C<foo> in
444 your class, you cannot override it with a delegated C<foo>. This is almost never
445 something you would want to do, and if it is, you should do it by hand and not
448 You cannot override any of the methods found in Moose::Object, or the C<BUILD>
449 and C<DEMOLISH> methods. These will not throw an exception, but will silently
450 move on to the next method in the list. My reasoning for this is that you would
451 almost never want to do this, since it usually breaks your class. As with
452 overriding locally defined methods, if you do want to do this, you should do it
453 manually, not with Moose.
455 You do not I<need> to have a reader (or accessor) for the attribute in order
456 to delegate to it. Moose will create a means of accessing the value for you,
457 however this will be several times B<less> efficient then if you had given
458 the attribute a reader (or accessor) to use.
460 Below is the documentation for each option format:
466 This is the most common usage for I<handles>. You basically pass a list of
467 method names to be delegated, and Moose will install a delegation method
472 This is the second most common usage for I<handles>. Instead of a list of
473 method names, you pass a HASH ref where each key is the method name you
474 want installed locally, and its value is the name of the original method
475 in the class being delegated to.
477 This can be very useful for recursive classes like trees. Here is a
478 quick example (soon to be expanded into a Moose::Cookbook recipe):
483 has 'node' => (is => 'rw', isa => 'Any');
488 default => sub { [] }
496 parent_node => 'node',
497 siblings => 'children',
501 In this example, the Tree package gets C<parent_node> and C<siblings> methods,
502 which delegate to the C<node> and C<children> methods (respectively) of the Tree
503 instance stored in the C<parent> slot.
507 The regexp option works very similar to the ARRAY option, except that it builds
508 the list of methods for you. It starts by collecting all possible methods of the
509 class being delegated to, then filters that list using the regexp supplied here.
511 B<NOTE:> An I<isa> option is required when using the regexp option format. This
512 is so that we can determine (at compile time) the method list from the class.
513 Without an I<isa> this is just not possible.
517 With the role option, you specify the name of a role whose "interface" then
518 becomes the list of methods to handle. The "interface" can be defined as; the
519 methods of the role and any required methods of the role. It should be noted
520 that this does B<not> include any method modifiers or generated attribute
521 methods (which is consistent with role composition).
525 This is the option to use when you really want to do something funky. You should
526 only use it if you really know what you are doing, as it involves manual
529 This takes a code reference, which should expect two arguments. The first is the
530 attribute meta-object this I<handles> is attached to. The second is the
531 metaclass of the class being delegated to. It expects you to return a hash (not
532 a HASH ref) of the methods you want mapped.
536 =item I<metaclass =E<gt> $metaclass_name>
538 This tells the class to use a custom attribute metaclass for this particular
539 attribute. Custom attribute metaclasses are useful for extending the
540 capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
541 but they are still a fairly advanced topic and too much to cover here, see
542 L<Moose::Cookbook::Meta::Recipe1> for more information.
544 The default behavior here is to just load C<$metaclass_name>; however, we also
545 have a way to alias to a shorter name. This will first look to see if
546 B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose
547 will then check to see if that has the method C<register_implementation>, which
548 should return the actual name of the custom attribute metaclass. If there is no
549 C<register_implementation> method, it will fall back to using
550 B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name.
552 =item I<traits =E<gt> [ @role_names ]>
554 This tells Moose to take the list of C<@role_names> and apply them to the
555 attribute meta-object. This is very similar to the I<metaclass> option, but
556 allows you to use more than one extension at a time.
558 See L<TRAIT NAME RESOLUTION> for details on how a trait name is
559 resolved to a class name.
561 Also see L<Moose::Cookbook::Meta::Recipe3> for a metaclass trait
566 =item B<has +$name =E<gt> %options>
568 This is variation on the normal attibute creator C<has> which allows you to
569 clone and extend an attribute from a superclass or from a role. Here is an
570 example of the superclass usage:
578 default => 'Hello, I am a Foo'
586 has '+message' => (default => 'Hello I am My::Foo');
588 What is happening here is that B<My::Foo> is cloning the C<message> attribute
589 from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt>
590 'Str'> characteristics, but changing the value in C<default>.
592 Here is another example, but within the context of a role:
600 default => 'Hello, I am a Foo'
608 has '+message' => (default => 'Hello I am My::Foo');
610 In this case, we are basically taking the attribute which the role supplied
611 and altering it within the bounds of this feature.
613 Aside from where the attributes come from (one from superclass, the other
614 from a role), this feature works exactly the same. This feature is restricted
615 somewhat, so as to try and force at least I<some> sanity into it. You are only
616 allowed to change the following attributes:
622 Change the default value of an attribute.
626 Change whether the attribute attempts to coerce a value passed to it.
630 Change if the attribute is required to have a value.
632 =item I<documentation>
634 Change the documentation string associated with the attribute.
638 Change if the attribute lazily initializes the slot.
642 You I<are> allowed to change the type without restriction.
644 It is recommended that you use this freedom with caution. We used to
645 only allow for extension only if the type was a subtype of the parent's
646 type, but we felt that was too restrictive and is better left as a
651 You are allowed to B<add> a new C<handles> definition, but you are B<not>
652 allowed to I<change> one.
656 You are allowed to B<add> a new C<builder> definition, but you are B<not>
657 allowed to I<change> one.
661 You are allowed to B<add> a new C<metaclass> definition, but you are
662 B<not> allowed to I<change> one.
666 You are allowed to B<add> additional traits to the C<traits> definition.
667 These traits will be composed into the attribute, but pre-existing traits
668 B<are not> overridden, or removed.
672 =item B<before $name|@names =E<gt> sub { ... }>
674 =item B<after $name|@names =E<gt> sub { ... }>
676 =item B<around $name|@names =E<gt> sub { ... }>
678 This three items are syntactic sugar for the before, after, and around method
679 modifier features that L<Class::MOP> provides. More information on these may be
680 found in the L<Class::MOP::Class documentation|Class::MOP::Class/"Method
685 The keyword C<super> is a no-op when called outside of an C<override> method. In
686 the context of an C<override> method, it will call the next most appropriate
687 superclass method with the same arguments as the original method.
689 =item B<override ($name, &sub)>
691 An C<override> method is a way of explicitly saying "I am overriding this
692 method from my superclass". You can call C<super> within this method, and
693 it will work as expected. The same thing I<can> be accomplished with a normal
694 method call and the C<SUPER::> pseudo-package; it is really your choice.
698 The keyword C<inner>, much like C<super>, is a no-op outside of the context of
699 an C<augment> method. You can think of C<inner> as being the inverse of
700 C<super>; the details of how C<inner> and C<augment> work is best described in
701 the L<Moose::Cookbook::Basics::Recipe6>.
703 =item B<augment ($name, &sub)>
705 An C<augment> method, is a way of explicitly saying "I am augmenting this
706 method from my superclass". Once again, the details of how C<inner> and
707 C<augment> work is best described in the L<Moose::Cookbook::Basics::Recipe6>.
711 This is the C<Carp::confess> function, and exported here because I use it
716 This is the C<Scalar::Util::blessed> function, it is exported here because I
717 use it all the time. It is highly recommended that this is used instead of
718 C<ref> anywhere you need to test for an object's class name.
722 =head1 METACLASS TRAITS
724 When you use Moose, you can also specify traits which will be applied
727 use Moose -traits => 'My::Trait';
729 This is very similar to the attribute traits feature. When you do
730 this, your class's C<meta> object will have the specified traits
731 applied to it. See L<TRAIT NAME RESOLUTION> for more details.
733 =head1 TRAIT NAME RESOLUTION
735 By default, when given a trait name, Moose simply tries to load a
736 class of the same name. If such a class does not exist, it then looks
737 for for a class matching
738 B<Moose::Meta::$type::Custom::Trait::$trait_name>. The C<$type>
739 variable here will be one of B<Attribute> or B<Class>, depending on
740 what the trait is being applied to.
742 If a class with this long name exists, Moose checks to see if it has
743 the method C<register_implementation>. This method is expected to
744 return the I<real> class name of the trait. If there is no
745 C<register_implementation> method, it will fall back to using
746 B<Moose::Meta::$type::Custom::Trait::$trait> as the trait name.
748 If all this is confusing, take a look at
749 L<Moose::Cookbook::Meta::Recipe3>, which demonstrates how to create an
752 =head1 UNIMPORTING FUNCTIONS
756 Moose offers a way to remove the keywords it exports, through the C<unimport>
757 method. You simply have to say C<no Moose> at the bottom of your code for this
758 to work. Here is an example:
763 has 'first_name' => (is => 'rw', isa => 'Str');
764 has 'last_name' => (is => 'rw', isa => 'Str');
768 $self->first_name . ' ' . $self->last_name
771 no Moose; # keywords are removed from the Person package
773 =head1 EXTENDING AND EMBEDDING MOOSE
775 Moose also offers some options for extending or embedding it into your
776 own framework. There are several things you might want to do as part
777 of such a framework. First, you probably want to export Moose's sugar
778 functions (C<has>, C<extends>, etc) for users of the
779 framework. Second, you may want to provide additional sugar of your
780 own. Third, you may want to provide your own object base class instead
781 of L<Moose::Object>, and/or your own metaclass class instead of
782 L<Moose::Meta::Class>.
784 The exporting needs can be asily satisfied by using
785 L<Moose::Exporter>, which is what C<Moose.pm> itself uses for
786 exporting. L<Moose::Exporter> lets you "export like Moose".
788 If you define an C<init_meta> method in a module that uses
789 L<Moose::Exporter>, then this method will be called I<before>
790 C<Moose.pm>'s own C<init_meta>. This gives you a chance to provide an
791 alternate object base class or metaclass class.
793 Here is a simple example:
800 use Moose (); # no need to get Moose's exports
803 Moose::Exporter->setup_import_methods( also => 'Moose' );
807 return Moose->init_meta( @_, base_class => 'MyFramework::Base' );
810 In this example, any class that includes C<use MyFramework> will get
811 all of C<Moose.pm>'s sugar functions, and will have their superclass
812 set to C<MyFramework::Base>.
814 Additionally, that class can include C<no MyFramework> to unimport
816 =head2 B<< Moose->init_meta(for_class => $class, base_class => $baseclass, metaclass => $metaclass) >>
818 The C<init_meta> method sets up the metaclass object for the class
819 specified by C<for_class>. This method injects a a C<meta> accessor
820 into the class so you can get at this object. It also sets the class's
821 superclass to C<base_class>, with L<Moose::Object> as the default.
823 You can specify an alternate metaclass with the C<metaclass> parameter.
825 For more detail on this topic, see L<Moose::Cookbook::Extending::Recipe2>.
827 This method used to be documented as a function which accepted
828 positional parameters. This calling style will still work for
829 backwards compatibility, but is deprecated.
833 Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
834 and C<{into_level =E<gt> 1}>.
836 B<NOTE>: Doing this is more or less deprecated. Use L<Moose::Exporter>
837 instead, which lets you stack multiple C<Moose.pm>-alike modules
838 sanely. It handles getting the exported functions into the right place
847 It should be noted that C<super> and C<inner> B<cannot> be used in the same
848 method. However, they may be combined within the same class hierarchy; see
849 F<t/014_override_augment_inner_super.t> for an example.
851 The reason for this is that C<super> is only valid within a method
852 with the C<override> modifier, and C<inner> will never be valid within an
853 C<override> method. In fact, C<augment> will skip over any C<override> methods
854 when searching for its appropriate C<inner>.
856 This might seem like a restriction, but I am of the opinion that keeping these
857 two features separate (yet interoperable) actually makes them easy to use, since
858 their behavior is then easier to predict. Time will tell whether I am right or
859 not (UPDATE: so far so good).
863 It is important to note that we currently have no simple way of combining
864 multiple extended versions of Moose (see L<EXTENDING AND EMBEDDING MOOSE> above),
865 and that in many cases they will conflict with one another. We are working on
866 developing a way around this issue, but in the meantime, you have been warned.
872 In case you are still asking yourself "Why do I need this?", then this
873 section is for you. This used to be part of the main DESCRIPTION, but
874 I think Moose no longer actually needs justification, so it is included
875 (read: buried) here for those who are still not convinced.
879 =item Another object system!?!?
881 Yes, I know there has been an explosion recently of new ways to
882 build objects in Perl 5, most of them based on inside-out objects
883 and other such things. Moose is different because it is not a new
884 object system for Perl 5, but instead an extension of the existing
887 Moose is built on top of L<Class::MOP>, which is a metaclass system
888 for Perl 5. This means that Moose not only makes building normal
889 Perl 5 objects better, but it also provides the power of metaclass
892 =item Is this for real? Or is this just an experiment?
894 Moose is I<based> on the prototypes and experiments I did for the Perl 6
895 meta-model. However, Moose is B<NOT> an experiment/prototype; it is for B<real>.
897 =item Is this ready for use in production?
899 Yes, I believe that it is.
901 Moose has been used successfully in production environemnts by several people
902 and companies (including the one I work for). There are Moose applications
903 which have been in production with little or no issue now for well over two years.
904 I consider it highly stable and we are commited to keeping it stable.
906 Of course, in the end, you need to make this call yourself. If you have
907 any questions or concerns, please feel free to email me, or even the list
908 or just stop by #moose and ask away.
910 =item Is Moose just Perl 6 in Perl 5?
912 No. While Moose is very much inspired by Perl 6, it is not itself Perl 6.
913 Instead, it is an OO system for Perl 5. I built Moose because I was tired of
914 writing the same old boring Perl 5 OO code, and drooling over Perl 6 OO. So
915 instead of switching to Ruby, I wrote Moose :)
917 =item Wait, I<post> modern, I thought it was just I<modern>?
919 So I was reading Larry Wall's talk from the 1999 Linux World entitled
920 "Perl, the first postmodern computer language" in which he talks about how
921 he picked the features for Perl because he thought they were cool and he
922 threw out the ones that he thought sucked. This got me thinking about how
923 we have done the same thing in Moose. For Moose, we have "borrowed" features
924 from Perl 6, CLOS (LISP), Smalltalk, Java, BETA, OCaml, Ruby and more, and
925 the bits we didn't like (cause they sucked) we tossed aside. So for this
926 reason (and a few others) I have re-dubbed Moose a I<postmodern> object system.
932 =head1 ACKNOWLEDGEMENTS
936 =item I blame Sam Vilain for introducing me to the insanity that is meta-models.
938 =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6.
940 =item Without Yuval "nothingmuch" Kogman this module would not be possible,
941 and it certainly wouldn't have this name ;P
943 =item The basis of the TypeContraints module was Rob Kinyon's idea
944 originally, I just ran with it.
946 =item Thanks to mst & chansen and the whole #moose posse for all the
947 early ideas/feature-requests/encouragement/bug-finding.
949 =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes.
957 =item L<http://www.iinteractive.com/moose>
959 This is the official web home of Moose, it contains links to our public SVN repo
960 as well as links to a number of talks and articles on Moose and Moose related
963 =item L<Moose::Cookbook> - How to cook a Moose
965 =item The Moose is flying, a tutorial by Randal Schwartz
967 Part 1 - L<http://www.stonehenge.com/merlyn/LinuxMag/col94.html>
969 Part 2 - L<http://www.stonehenge.com/merlyn/LinuxMag/col95.html>
971 =item L<Class::MOP> documentation
973 =item The #moose channel on irc.perl.org
975 =item The Moose mailing list - moose@perl.org
977 =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/moose>
979 =item Several Moose extension modules in the C<MooseX::> namespace.
981 See L<http://search.cpan.org/search?query=MooseX::> for extensions.
989 =item The Art of the MetaObject Protocol
991 I mention this in the L<Class::MOP> docs too, this book was critical in
992 the development of both modules and is highly recommended.
1000 =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf>
1002 This paper (suggested by lbr on #moose) was what lead to the implementation
1003 of the C<super>/C<override> and C<inner>/C<augment> features. If you really
1004 want to understand them, I suggest you read this.
1010 All complex software has bugs lurking in it, and this module is no
1011 exception. If you find a bug please either email me, or add the bug
1014 =head1 FEATURE REQUESTS
1016 We are very strict about what features we add to the Moose core, especially
1017 the user-visible features. Instead we have made sure that the underlying
1018 meta-system of Moose is as extensible as possible so that you can add your
1019 own features easily. That said, occasionally there is a feature needed in the
1020 meta-system to support your planned extension, in which case you should
1021 either email the mailing list or join us on irc at #moose to discuss.
1025 Stevan Little E<lt>stevan@iinteractive.comE<gt>
1027 B<with contributions from:>
1031 Adam (Alias) Kennedy
1033 Anders (Debolaz) Nor Berle
1035 Nathan (kolibre) Gray
1037 Christian (chansen) Hansen
1039 Hans Dieter (confound) Pearcey
1041 Eric (ewilhelm) Wilhelm
1043 Guillermo (groditi) Roditi
1045 Jess (castaway) Robinson
1049 Robert (phaylon) Sedlacek
1053 Scott (konobi) McWhirter
1055 Shlomi (rindolf) Fish
1057 Yuval (nothingmuch) Kogman
1059 Chris (perigrin) Prather
1061 Wallace (wreis) Reis
1063 Jonathan (jrockway) Rockway
1065 Piotr (dexter) Roszatycki
1067 Sam (mugwump) Vilain
1069 Shawn (sartak) Moore
1071 ... and many other #moose folks
1073 =head1 COPYRIGHT AND LICENSE
1075 Copyright 2006-2008 by Infinity Interactive, Inc.
1077 L<http://www.iinteractive.com>
1079 This library is free software; you can redistribute it and/or modify
1080 it under the same terms as Perl itself.