8 our $AUTHORITY = 'cpan:STEVAN';
10 use Scalar::Util 'blessed', 'reftype';
11 use Carp 'confess', 'croak';
12 use Sub::Name 'subname';
19 use Moose::Meta::Class;
20 use Moose::Meta::TypeConstraint;
21 use Moose::Meta::TypeCoercion;
22 use Moose::Meta::Attribute;
23 use Moose::Meta::Instance;
25 use Moose::Meta::Role;
28 use Moose::Util::TypeConstraints;
35 my ( $class, $base_class, $metaclass ) = @_;
36 $base_class = 'Moose::Object' unless defined $base_class;
37 $metaclass = 'Moose::Meta::Class' unless defined $metaclass;
40 "The Metaclass $metaclass must be a subclass of Moose::Meta::Class."
41 unless $metaclass->isa('Moose::Meta::Class');
43 # make a subtype for each Moose class
45 unless find_type_constraint($class);
48 if ( $class->can('meta') ) {
50 # this is the case where the metaclass pragma
51 # was used before the 'use Moose' statement to
52 # override a specific class
53 $meta = $class->meta();
54 ( blessed($meta) && $meta->isa('Moose::Meta::Class') )
55 || confess "You already have a &meta function, but it does not return a Moose::Meta::Class";
59 # this is broken currently, we actually need
60 # to allow the possiblity of an inherited
61 # meta, which will not be visible until the
62 # user 'extends' first. This needs to have
63 # more intelligence to it
64 $meta = $metaclass->initialize($class);
67 # re-initialize so it inherits properly
68 $metaclass->initialize( blessed( $_[0] ) || $_[0] );
73 # make sure they inherit from Moose::Object
74 $meta->superclasses($base_class)
75 unless $meta->superclasses();
83 return subname 'Moose::extends' => sub (@) {
84 confess "Must derive at least one class" unless @_;
87 foreach my $super (@supers) {
88 Class::MOP::load_class($super);
91 # this checks the metaclass to make sure
92 # it is correct, sometimes it can get out
93 # of sync when the classes are being built
94 my $meta = $class->meta->_fix_metaclass_incompatability(@supers);
95 $meta->superclasses(@supers);
100 return subname 'Moose::with' => sub (@) {
101 Moose::Util::apply_all_roles($class->meta, @_)
106 return subname 'Moose::has' => sub ($;%) {
108 croak 'Usage: has \'name\' => ( key => value, ... )' if @_ == 1;
110 my $attrs = ( ref($name) eq 'ARRAY' ) ? $name : [ ($name) ];
111 $class->meta->add_attribute( $_, %options ) for @$attrs;
116 return subname 'Moose::before' => sub (@&) {
118 my $meta = $class->meta;
119 $meta->add_before_method_modifier( $_, $code ) for @_;
124 return subname 'Moose::after' => sub (@&) {
126 my $meta = $class->meta;
127 $meta->add_after_method_modifier( $_, $code ) for @_;
132 return subname 'Moose::around' => sub (@&) {
134 my $meta = $class->meta;
135 $meta->add_around_method_modifier( $_, $code ) for @_;
139 # FIXME can be made into goto, might break caller() for existing code
140 return subname 'Moose::super' => sub { return unless our $SUPER_BODY; $SUPER_BODY->(our @SUPER_ARGS) }
143 # return subname 'Moose::next' => sub { @_ = our @SUPER_ARGS; goto \&next::method };
147 return subname 'Moose::override' => sub ($&) {
148 my ( $name, $method ) = @_;
149 $class->meta->add_override_method_modifier( $name => $method );
153 return subname 'Moose::inner' => sub {
155 our ( %INNER_BODY, %INNER_ARGS );
157 if ( my $body = $INNER_BODY{$pkg} ) {
158 my @args = @{ $INNER_ARGS{$pkg} };
159 local $INNER_ARGS{$pkg};
160 local $INNER_BODY{$pkg};
161 return $body->(@args);
169 return subname 'Moose::augment' => sub (@&) {
170 my ( $name, $method ) = @_;
171 $class->meta->add_augment_method_modifier( $name => $method );
174 make_immutable => sub {
176 return subname 'Moose::make_immutable' => sub {
177 warn "The make_immutable keyword has been deprecated, " .
178 "please go back to __PACKAGE__->meta->make_immutable\n";
179 $class->meta->make_immutable(@_);
183 return \&Carp::confess;
186 return \&Scalar::Util::blessed;
190 my $exporter = Sub::Exporter::build_exporter(
192 exports => \%exports,
193 groups => { default => [':all'] }
197 # 1 extra level because it's called by import so there's a layer of indirection
201 ref $_[1] && defined $_[1]->{into}
203 : ref $_[1] && defined $_[1]->{into_level}
204 ? caller($offset + $_[1]->{into_level})
209 $CALLER = _get_caller(@_);
211 # this works because both pragmas set $^H (see perldoc perlvar)
212 # which affects the current compilation - i.e. the file who use'd
213 # us - which is why we don't need to do anything special to make
214 # it affect that file rather than this one (which is already compiled)
219 # we should never export to main
220 return if $CALLER eq 'main';
222 init_meta( $CALLER, 'Moose::Object' );
229 my $class = _get_caller(@_);
231 # loop through the exports ...
232 foreach my $name ( keys %exports ) {
235 if ( defined &{ $class . '::' . $name } ) {
236 my $keyword = \&{ $class . '::' . $name };
238 # make sure it is from Moose
239 my ($pkg_name) = Class::MOP::get_code_info($keyword);
241 next if $pkg_name ne 'Moose';
243 # and if it is from Moose then undef the slot
244 delete ${ $class . '::' }{$name};
251 ## make 'em all immutable
253 $_->meta->make_immutable(
254 inline_constructor => 0,
255 inline_accessors => 1, # these are Class::MOP accessors, so they need inlining
258 'Moose::Meta::Attribute',
259 'Moose::Meta::Class',
260 'Moose::Meta::Instance',
262 'Moose::Meta::TypeConstraint',
263 'Moose::Meta::TypeConstraint::Union',
264 'Moose::Meta::TypeConstraint::Parameterized',
265 'Moose::Meta::TypeCoercion',
267 'Moose::Meta::Method',
268 'Moose::Meta::Method::Accessor',
269 'Moose::Meta::Method::Constructor',
270 'Moose::Meta::Method::Destructor',
271 'Moose::Meta::Method::Overriden',
274 'Moose::Meta::Role::Method',
275 'Moose::Meta::Role::Method::Required',
286 Moose - A postmodern object system for Perl 5
291 use Moose; # automatically turns on strict and warnings
293 has 'x' => (is => 'rw', isa => 'Int');
294 has 'y' => (is => 'rw', isa => 'Int');
307 has 'z' => (is => 'rw', isa => 'Int');
309 after 'clear' => sub {
316 Moose is an extension of the Perl 5 object system.
318 =head2 Another object system!?!?
320 Yes, I know there has been an explosion recently of new ways to
321 build object's in Perl 5, most of them based on inside-out objects
322 and other such things. Moose is different because it is not a new
323 object system for Perl 5, but instead an extension of the existing
326 Moose is built on top of L<Class::MOP>, which is a metaclass system
327 for Perl 5. This means that Moose not only makes building normal
328 Perl 5 objects better, but it also provides the power of metaclass
331 =head2 Is this for real? Or is this just an experiment?
333 Moose is I<based> on the prototypes and experiments I did for the Perl 6
334 meta-model. However, Moose is B<NOT> an experiment/prototype; it is for B<real>.
336 =head2 Is this ready for use in production?
338 Yes, I believe that it is.
340 Moose has been used successfully in production environemnts by several people
341 and companies (including the one I work for). There are Moose applications
342 which have been in production with little or no issue now for well over a year.
343 I consider it highly stable and we are commited to keeping it stable.
345 Of course, in the end, you need to make this call yourself. If you have
346 any questions or concerns, please feel free to email me, or even the list
347 or just stop by #moose and ask away.
349 =head2 Is Moose just Perl 6 in Perl 5?
351 No. While Moose is very much inspired by Perl 6, it is not itself Perl 6.
352 Instead, it is an OO system for Perl 5. I built Moose because I was tired of
353 writing the same old boring Perl 5 OO code, and drooling over Perl 6 OO. So
354 instead of switching to Ruby, I wrote Moose :)
356 =head2 Wait, I<post> modern, I thought it was just I<modern>?
358 So I was reading Larry Wall's talk from the 1999 Linux World entitled
359 "Perl, the first postmodern computer language" in which he talks about how
360 he picked the features for Perl because he thought they were cool and he
361 threw out the ones that he thought sucked. This got me thinking about how
362 we have done the same thing in Moose. For Moose, we have "borrowed" features
363 from Perl 6, CLOS (LISP), Smalltalk, Java, BETA, OCaml, Ruby and more, and
364 the bits we didn't like (cause they sucked) we tossed aside. So for this
365 reason (and a few others) I have re-dubbed Moose a I<postmodern> object system.
369 =head2 Moose Extensions
371 The L<MooseX::> namespace is the official place to find Moose extensions.
372 There are a number of these modules out on CPAN right now the best way to
373 find them is to search for MooseX:: on search.cpan.org.
375 =head1 BUILDING CLASSES WITH MOOSE
377 Moose makes every attempt to provide as much convenience as possible during
378 class construction/definition, but still stay out of your way if you want it
379 to. Here are a few items to note when building classes with Moose.
381 Unless specified with C<extends>, any class which uses Moose will
382 inherit from L<Moose::Object>.
384 Moose will also manage all attributes (including inherited ones) that are
385 defined with C<has>. And (assuming you call C<new>, which is inherited from
386 L<Moose::Object>) this includes properly initializing all instance slots,
387 setting defaults where appropriate, and performing any type constraint checking
390 =head1 PROVIDED METHODS
392 Moose provides a number of methods to all your classes, mostly through the
393 inheritance of L<Moose::Object>. There is however, one exception.
399 This is a method which provides access to the current class's metaclass.
403 =head1 EXPORTED FUNCTIONS
405 Moose will export a number of functions into the class's namespace which
406 may then be used to set up the class. These functions all work directly
407 on the current class.
411 =item B<extends (@superclasses)>
413 This function will set the superclass(es) for the current class.
415 This approach is recommended instead of C<use base>, because C<use base>
416 actually C<push>es onto the class's C<@ISA>, whereas C<extends> will
417 replace it. This is important to ensure that classes which do not have
418 superclasses still properly inherit from L<Moose::Object>.
420 =item B<with (@roles)>
422 This will apply a given set of C<@roles> to the local class.
424 =item B<has $name =E<gt> %options>
426 This will install an attribute of a given C<$name> into the current class.
427 The C<%options> are the same as those provided by
428 L<Class::MOP::Attribute>, in addition to the list below which are provided
429 by Moose (L<Moose::Meta::Attribute> to be more specific):
433 =item I<is =E<gt> 'rw'|'ro'>
435 The I<is> option accepts either I<rw> (for read/write) or I<ro> (for read
436 only). These will create either a read/write accessor or a read-only
437 accessor respectively, using the same name as the C<$name> of the attribute.
439 If you need more control over how your accessors are named, you can use the
440 I<reader>, I<writer> and I<accessor> options inherited from
441 L<Class::MOP::Attribute>, however if you use those, you won't need the I<is>
444 =item I<isa =E<gt> $type_name>
446 The I<isa> option uses Moose's type constraint facilities to set up runtime
447 type checking for this attribute. Moose will perform the checks during class
448 construction, and within any accessors. The C<$type_name> argument must be a
449 string. The string may be either a class name or a type defined using
450 Moose's type definition features. (Refer to L<Moose::Util::TypeConstraints>
451 for information on how to define a new type, and how to retrieve type meta-data).
453 =item I<coerce =E<gt> (1|0)>
455 This will attempt to use coercion with the supplied type constraint to change
456 the value passed into any accessors or constructors. You B<must> have supplied
457 a type constraint in order for this to work. See L<Moose::Cookbook::Recipe5>
460 =item I<does =E<gt> $role_name>
462 This will accept the name of a role which the value stored in this attribute
463 is expected to have consumed.
465 =item I<required =E<gt> (1|0)>
467 This marks the attribute as being required. This means a I<defined> value must be
468 supplied during class construction, and the attribute may never be set to
469 C<undef> with an accessor.
471 =item I<weak_ref =E<gt> (1|0)>
473 This will tell the class to store the value of this attribute as a weakened
474 reference. If an attribute is a weakened reference, it B<cannot> also be
477 =item I<lazy =E<gt> (1|0)>
479 This will tell the class to not create this slot until absolutely necessary.
480 If an attribute is marked as lazy it B<must> have a default supplied.
482 =item I<auto_deref =E<gt> (1|0)>
484 This tells the accessor whether to automatically dereference the value returned.
485 This is only legal if your C<isa> option is either C<ArrayRef> or C<HashRef>.
487 =item I<trigger =E<gt> $code>
489 The I<trigger> option is a CODE reference which will be called after the value of
490 the attribute is set. The CODE ref will be passed the instance itself, the
491 updated value and the attribute meta-object (this is for more advanced fiddling
492 and can typically be ignored). You B<cannot> have a trigger on a read-only
495 =item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
497 The I<handles> option provides Moose classes with automated delegation features.
498 This is a pretty complex and powerful option. It accepts many different option
499 formats, each with its own benefits and drawbacks.
501 B<NOTE:> The class being delegated to does not need to be a Moose based class,
502 which is why this feature is especially useful when wrapping non-Moose classes.
504 All I<handles> option formats share the following traits:
506 You cannot override a locally defined method with a delegated method; an
507 exception will be thrown if you try. That is to say, if you define C<foo> in
508 your class, you cannot override it with a delegated C<foo>. This is almost never
509 something you would want to do, and if it is, you should do it by hand and not
512 You cannot override any of the methods found in Moose::Object, or the C<BUILD>
513 and C<DEMOLISH> methods. These will not throw an exception, but will silently
514 move on to the next method in the list. My reasoning for this is that you would
515 almost never want to do this, since it usually breaks your class. As with
516 overriding locally defined methods, if you do want to do this, you should do it
517 manually, not with Moose.
519 You do not I<need> to have a reader (or accessor) for the attribute in order
520 to delegate to it. Moose will create a means of accessing the value for you,
521 however this will be several times B<less> efficient then if you had given
522 the attribute a reader (or accessor) to use.
524 Below is the documentation for each option format:
530 This is the most common usage for I<handles>. You basically pass a list of
531 method names to be delegated, and Moose will install a delegation method
536 This is the second most common usage for I<handles>. Instead of a list of
537 method names, you pass a HASH ref where each key is the method name you
538 want installed locally, and its value is the name of the original method
539 in the class being delegated to.
541 This can be very useful for recursive classes like trees. Here is a
542 quick example (soon to be expanded into a Moose::Cookbook::Recipe):
547 has 'node' => (is => 'rw', isa => 'Any');
552 default => sub { [] }
560 parent_node => 'node',
561 siblings => 'children',
565 In this example, the Tree package gets C<parent_node> and C<siblings> methods,
566 which delegate to the C<node> and C<children> methods (respectively) of the Tree
567 instance stored in the C<parent> slot.
571 The regexp option works very similar to the ARRAY option, except that it builds
572 the list of methods for you. It starts by collecting all possible methods of the
573 class being delegated to, then filters that list using the regexp supplied here.
575 B<NOTE:> An I<isa> option is required when using the regexp option format. This
576 is so that we can determine (at compile time) the method list from the class.
577 Without an I<isa> this is just not possible.
581 With the role option, you specify the name of a role whose "interface" then
582 becomes the list of methods to handle. The "interface" can be defined as; the
583 methods of the role and any required methods of the role. It should be noted
584 that this does B<not> include any method modifiers or generated attribute
585 methods (which is consistent with role composition).
589 This is the option to use when you really want to do something funky. You should
590 only use it if you really know what you are doing, as it involves manual
593 This takes a code reference, which should expect two arguments. The first is the
594 attribute meta-object this I<handles> is attached to. The second is the
595 metaclass of the class being delegated to. It expects you to return a hash (not
596 a HASH ref) of the methods you want mapped.
600 =item I<metaclass =E<gt> $metaclass_name>
602 This tells the class to use a custom attribute metaclass for this particular
603 attribute. Custom attribute metaclasses are useful for extending the
604 capabilities of the I<has> keyword: they are the simplest way to extend the MOP,
605 but they are still a fairly advanced topic and too much to cover here, see
606 L<Moose::Cookbook::Recipe11> for more information.
608 The default behavior here is to just load C<$metaclass_name>; however, we also
609 have a way to alias to a shorter name. This will first look to see if
610 B<Moose::Meta::Attribute::Custom::$metaclass_name> exists. If it does, Moose
611 will then check to see if that has the method C<register_implementation>, which
612 should return the actual name of the custom attribute metaclass. If there is no
613 C<register_implementation> method, it will fall back to using
614 B<Moose::Meta::Attribute::Custom::$metaclass_name> as the metaclass name.
616 =item I<traits =E<gt> [ @role_names ]>
618 This tells Moose to take the list of C<@role_names> and apply them to the
619 attribute meta-object. This is very similar to the I<metaclass> option, but
620 allows you to use more than one extension at a time. This too is an advanced
621 topic, we don't yet have a cookbook for it though.
623 As with I<metaclass>, the default behavior is to just load C<$role_name>; however,
624 we also have a way to alias to a shorter name. This will first look to see if
625 B<Moose::Meta::Attribute::Custom::Trait::$role_name> exists. If it does, Moose
626 will then check to see if that has the method C<register_implementation>, which
627 should return the actual name of the custom attribute trait. If there is no
628 C<register_implementation> method, it will fall back to using
629 B<Moose::Meta::Attribute::Custom::Trait::$metaclass_name> as the trait name.
633 =item B<has +$name =E<gt> %options>
635 This is variation on the normal attibute creator C<has> which allows you to
636 clone and extend an attribute from a superclass or from a role. Here is an
637 example of the superclass usage:
645 default => 'Hello, I am a Foo'
653 has '+message' => (default => 'Hello I am My::Foo');
655 What is happening here is that B<My::Foo> is cloning the C<message> attribute
656 from its parent class B<Foo>, retaining the C<is =E<gt> 'rw'> and C<isa =E<gt>
657 'Str'> characteristics, but changing the value in C<default>.
659 Here is another example, but within the context of a role:
667 default => 'Hello, I am a Foo'
675 has '+message' => (default => 'Hello I am My::Foo');
677 In this case, we are basically taking the attribute which the role supplied
678 and altering it within the bounds of this feature.
680 Aside from where the attributes come from (one from superclass, the other
681 from a role), this feature works exactly the same. This feature is restricted
682 somewhat, so as to try and force at least I<some> sanity into it. You are only
683 allowed to change the following attributes:
689 Change the default value of an attribute.
693 Change whether the attribute attempts to coerce a value passed to it.
697 Change if the attribute is required to have a value.
699 =item I<documentation>
701 Change the documentation string associated with the attribute.
705 Change if the attribute lazily initializes the slot.
709 You I<are> allowed to change the type without restriction.
711 It is recommended that you use this freedom with caution. We used to
712 only allow for extension only if the type was a subtype of the parent's
713 type, but we felt that was too restrictive and is better left as a
718 You are allowed to B<add> a new C<handles> definition, but you are B<not>
719 allowed to I<change> one.
723 You are allowed to B<add> a new C<builder> definition, but you are B<not>
724 allowed to I<change> one.
728 =item B<before $name|@names =E<gt> sub { ... }>
730 =item B<after $name|@names =E<gt> sub { ... }>
732 =item B<around $name|@names =E<gt> sub { ... }>
734 This three items are syntactic sugar for the before, after, and around method
735 modifier features that L<Class::MOP> provides. More information on these may be
736 found in the L<Class::MOP::Class documentation|Class::MOP::Class/"Method
741 The keyword C<super> is a no-op when called outside of an C<override> method. In
742 the context of an C<override> method, it will call the next most appropriate
743 superclass method with the same arguments as the original method.
745 =item B<override ($name, &sub)>
747 An C<override> method is a way of explicitly saying "I am overriding this
748 method from my superclass". You can call C<super> within this method, and
749 it will work as expected. The same thing I<can> be accomplished with a normal
750 method call and the C<SUPER::> pseudo-package; it is really your choice.
754 The keyword C<inner>, much like C<super>, is a no-op outside of the context of
755 an C<augment> method. You can think of C<inner> as being the inverse of
756 C<super>; the details of how C<inner> and C<augment> work is best described in
757 the L<Moose::Cookbook::Recipe7>.
759 =item B<augment ($name, &sub)>
761 An C<augment> method, is a way of explicitly saying "I am augmenting this
762 method from my superclass". Once again, the details of how C<inner> and
763 C<augment> work is best described in the L<Moose::Cookbook::Recipe7>.
767 This is the C<Carp::confess> function, and exported here because I use it
772 This is the C<Scalar::Util::blessed> function, it is exported here because I
773 use it all the time. It is highly recommended that this is used instead of
774 C<ref> anywhere you need to test for an object's class name.
778 =head1 UNIMPORTING FUNCTIONS
782 Moose offers a way to remove the keywords it exports, through the C<unimport>
783 method. You simply have to say C<no Moose> at the bottom of your code for this
784 to work. Here is an example:
789 has 'first_name' => (is => 'rw', isa => 'Str');
790 has 'last_name' => (is => 'rw', isa => 'Str');
794 $self->first_name . ' ' . $self->last_name
797 no Moose; # keywords are removed from the Person package
799 =head1 EXTENDING AND EMBEDDING MOOSE
801 Moose also offers some options for extending or embedding it into your own
802 framework. The basic premise is to have something that sets up your class'
803 metaclass and export the moose declarators (C<has>, C<with>, C<extends>,...).
810 my $CALLER = caller();
815 # we should never export to main
816 return if $CALLER eq 'main';
817 Moose::init_meta( $CALLER, 'MyFramework::Base' );
818 Moose->import({into => $CALLER});
820 # Do my custom framework stuff
827 Moose's C<import> method supports the L<Sub::Exporter> form of C<{into =E<gt> $pkg}>
828 and C<{into_level =E<gt> 1}>
830 =head2 B<init_meta ($class, $baseclass, $metaclass)>
832 Moose does some boot strapping: it creates a metaclass object for your class,
833 and then injects a C<meta> accessor into your class to retrieve it. Then it
834 sets your baseclass to Moose::Object or the value you pass in unless you already
835 have one. This is all done via C<init_meta> which takes the name of your class
836 and optionally a baseclass and a metaclass as arguments.
844 It should be noted that C<super> and C<inner> B<cannot> be used in the same
845 method. However, they may be combined within the same class hierarchy; see
846 F<t/014_override_augment_inner_super.t> for an example.
848 The reason for this is that C<super> is only valid within a method
849 with the C<override> modifier, and C<inner> will never be valid within an
850 C<override> method. In fact, C<augment> will skip over any C<override> methods
851 when searching for its appropriate C<inner>.
853 This might seem like a restriction, but I am of the opinion that keeping these
854 two features separate (yet interoperable) actually makes them easy to use, since
855 their behavior is then easier to predict. Time will tell whether I am right or
856 not (UPDATE: so far so good).
860 It is important to note that we currently have no simple way of combining
861 multiple extended versions of Moose (see L<EXTENDING AND EMBEDDING MOOSE> above),
862 and that in many cases they will conflict with one another. We are working on
863 developing a way around this issue, but in the meantime, you have been warned.
867 =head1 ACKNOWLEDGEMENTS
871 =item I blame Sam Vilain for introducing me to the insanity that is meta-models.
873 =item I blame Audrey Tang for then encouraging my meta-model habit in #perl6.
875 =item Without Yuval "nothingmuch" Kogman this module would not be possible,
876 and it certainly wouldn't have this name ;P
878 =item The basis of the TypeContraints module was Rob Kinyon's idea
879 originally, I just ran with it.
881 =item Thanks to mst & chansen and the whole #moose posse for all the
882 early ideas/feature-requests/encouragement/bug-finding.
884 =item Thanks to David "Theory" Wheeler for meta-discussions and spelling fixes.
892 =item L<http://www.iinteractive.com/moose>
894 This is the official web home of Moose, it contains links to our public SVN repo
895 as well as links to a number of talks and articles on Moose and Moose related
898 =item L<Class::MOP> documentation
900 =item The #moose channel on irc.perl.org
902 =item The Moose mailing list - moose@perl.org
904 =item Moose stats on ohloh.net - L<http://www.ohloh.net/projects/5788>
906 =item Several Moose extension modules in the L<MooseX::> namespace.
914 =item The Art of the MetaObject Protocol
916 I mention this in the L<Class::MOP> docs too, this book was critical in
917 the development of both modules and is highly recommended.
925 =item L<http://www.cs.utah.edu/plt/publications/oopsla04-gff.pdf>
927 This paper (suggested by lbr on #moose) was what lead to the implementation
928 of the C<super>/C<override> and C<inner>/C<augment> features. If you really
929 want to understand them, I suggest you read this.
935 All complex software has bugs lurking in it, and this module is no
936 exception. If you find a bug please either email me, or add the bug
941 Stevan Little E<lt>stevan@iinteractive.comE<gt>
943 B<with contributions from:>
949 Anders (Debolaz) Nor Berle
951 Nathan (kolibre) Gray
953 Christian (chansen) Hansen
955 Hans Dieter (confound) Pearcey
957 Eric (ewilhelm) Wilhelm
959 Guillermo (groditi) Roditi
961 Jess (castaway) Robinson
965 Robert (phaylon) Sedlacek
969 Scott (konobi) McWhirter
971 Shlomi (rindolf) Fish
973 Yuval (nothingmuch) Kogman
975 Chris (perigrin) Prather
977 Jonathan (jrockway) Rockway
979 Piotr (dexter) Roszatycki
985 ... and many other #moose folks
987 =head1 COPYRIGHT AND LICENSE
989 Copyright 2006-2008 by Infinity Interactive, Inc.
991 L<http://www.iinteractive.com>
993 This library is free software; you can redistribute it and/or modify
994 it under the same terms as Perl itself.