8 our $VERSION = '1.002000'; # 1.2.0
9 $VERSION = eval $VERSION;
11 require Moo::sification;
15 sub _install_tracked {
16 my ($target, $name, $code) = @_;
17 $MAKERS{$target}{exports}{$name} = $code;
18 _install_coderef "${target}::${name}" => "Moo::${name}" => $code;
25 if ($Moo::Role::INFO{$target} and $Moo::Role::INFO{$target}{is_role}) {
26 die "Cannot import Moo into a role";
28 $MAKERS{$target} ||= {};
29 _install_tracked $target => extends => sub {
30 $class->_set_superclasses($target, @_);
31 $class->_maybe_reset_handlemoose($target);
34 _install_tracked $target => with => sub {
36 Moo::Role->apply_roles_to_package($target, @_);
37 $class->_maybe_reset_handlemoose($target);
39 _install_tracked $target => has => sub {
40 my ($name_proto, %spec) = @_;
41 my $name_isref = ref $name_proto eq 'ARRAY';
42 foreach my $name ($name_isref ? @$name_proto : $name_proto) {
43 # Note that when $name_proto is an arrayref, each attribute
44 # needs a separate \%specs hashref
45 my $spec_ref = $name_isref ? +{%spec} : \%spec;
46 $class->_constructor_maker_for($target)
47 ->register_attribute_specs($name, $spec_ref);
48 $class->_accessor_maker_for($target)
49 ->generate_method($target, $name, $spec_ref);
50 $class->_maybe_reset_handlemoose($target);
54 foreach my $type (qw(before after around)) {
55 _install_tracked $target => $type => sub {
56 require Class::Method::Modifiers;
57 _install_modifier($target, $type, @_);
61 return if $MAKERS{$target}{is_class}; # already exported into this package
62 $MAKERS{$target}{is_class} = 1;
65 @{"${target}::ISA"} = do {
66 require Moo::Object; ('Moo::Object');
67 } unless @{"${target}::ISA"};
69 if ($INC{'Moo/HandleMoose.pm'}) {
70 Moo::HandleMoose::inject_fake_metaclass_for($target);
76 _unimport_coderefs($target, $MAKERS{$target});
79 sub _set_superclasses {
82 foreach my $superclass (@_) {
83 _load_module($superclass);
84 if ($INC{"Role/Tiny.pm"} && $Role::Tiny::INFO{$superclass}) {
86 Carp::croak("Can't extend role '$superclass'");
89 # Can't do *{...} = \@_ or 5.10.0's mro.pm stops seeing @ISA
90 @{*{_getglob("${target}::ISA")}{ARRAY}} = @_;
91 if (my $old = delete $Moo::MAKERS{$target}{constructor}) {
92 delete _getstash($target)->{new};
93 Moo->_constructor_maker_for($target)
94 ->register_attribute_specs(%{$old->all_attribute_specs});
96 elsif (!$target->isa('Moo::Object')) {
97 Moo->_constructor_maker_for($target);
99 no warnings 'once'; # piss off. -- mst
100 $Moo::HandleMoose::MOUSE{$target} = [
101 grep defined, map Mouse::Util::find_meta($_), @_
102 ] if Mouse::Util->can('find_meta');
105 sub _maybe_reset_handlemoose {
106 my ($class, $target) = @_;
107 if ($INC{"Moo/HandleMoose.pm"}) {
108 Moo::HandleMoose::maybe_reinject_fake_metaclass_for($target);
112 sub _accessor_maker_for {
113 my ($class, $target) = @_;
114 return unless $MAKERS{$target};
115 $MAKERS{$target}{accessor} ||= do {
116 my $maker_class = do {
118 if (my $defer_target =
119 (Sub::Defer::defer_info($target->can('new'))||[])->[0]
121 my ($pkg) = ($defer_target =~ /^(.*)::[^:]+$/);
122 $MAKERS{$pkg} && $MAKERS{$pkg}{accessor};
129 require Method::Generate::Accessor;
130 'Method::Generate::Accessor'
137 sub _constructor_maker_for {
138 my ($class, $target, $select_super) = @_;
139 return unless $MAKERS{$target};
140 $MAKERS{$target}{constructor} ||= do {
141 require Method::Generate::Constructor;
143 my ($moo_constructor, $con);
145 if ($select_super && $MAKERS{$select_super}) {
146 $moo_constructor = 1;
147 $con = $MAKERS{$select_super}{constructor};
149 my $t_new = $target->can('new');
151 if ($t_new == Moo::Object->can('new')) {
152 $moo_constructor = 1;
153 } elsif (my $defer_target = (Sub::Defer::defer_info($t_new)||[])->[0]) {
154 my ($pkg) = ($defer_target =~ /^(.*)::[^:]+$/);
156 $moo_constructor = 1;
157 $con = $MAKERS{$pkg}{constructor};
161 $moo_constructor = 1; # no other constructor, make a Moo one
164 ($con ? ref($con) : 'Method::Generate::Constructor')
167 accessor_generator => $class->_accessor_maker_for($target),
168 construction_string => (
170 ? ($con ? $con->construction_string : undef)
171 : ('$class->'.$target.'::SUPER::new($class->can(q[FOREIGNBUILDARGS]) ? $class->FOREIGNBUILDARGS(@_) : @_)')
173 subconstructor_handler => (
174 ' if ($Moo::MAKERS{$class}) {'."\n"
175 .' '.$class.'->_constructor_maker_for($class,'.perlstring($target).');'."\n"
176 .' return $class->new(@_)'.";\n"
177 .' } elsif ($INC{"Moose.pm"} and my $meta = Class::MOP::get_metaclass_by_name($class)) {'."\n"
178 .' return $meta->new_object($class->BUILDARGS(@_));'."\n"
183 ->register_attribute_specs(%{$con?$con->all_attribute_specs:{}})
194 Moo - Minimalist Object Orientation (with Moose compatibility)
204 my $amount = shift || 1;
206 $self->pounds( $self->pounds - $amount );
216 die "Only SWEET-TREATZ supported!" unless $_[0] eq 'SWEET-TREATZ'
222 isa => sub { die "$_[0] is too much cat food!" unless $_[0] < 15 },
229 my $full = Cat::Food->new(
230 taste => 'DELICIOUS.',
231 brand => 'SWEET-TREATZ',
241 This module is an extremely light-weight subset of L<Moose> optimised for
242 rapid startup and "pay only for what you use".
244 It also avoids depending on any XS modules to allow simple deployments. The
245 name C<Moo> is based on the idea that it provides almost -- but not quite -- two
248 Unlike L<Mouse> this module does not aim at full compatibility with
249 L<Moose>'s surface syntax, preferring instead of provide full interoperability
250 via the metaclass inflation capabilities described in L</MOO AND MOOSE>.
252 For a full list of the minor differences between L<Moose> and L<Moo>'s surface
253 syntax, see L</INCOMPATIBILITIES WITH MOOSE>.
255 =head1 WHY MOO EXISTS
257 If you want a full object system with a rich Metaprotocol, L<Moose> is
260 However, sometimes you're writing a command line script or a CGI script
261 where fast startup is essential, or code designed to be deployed as a single
262 file via L<App::FatPacker>, or you're writing a CPAN module and you want it
263 to be usable by people with those constraints.
265 I've tried several times to use L<Mouse> but it's 3x the size of Moo and
266 takes longer to load than most of my Moo based CGI scripts take to run.
268 If you don't want L<Moose>, you don't want "less metaprotocol" like L<Mouse>,
269 you want "as little as possible" -- which means "no metaprotocol", which is
272 Better still, if you install and load L<Moose>, we set up metaclasses for your
273 L<Moo> classes and L<Moo::Role> roles, so you can use them in L<Moose> code
274 without ever noticing that some of your codebase is using L<Moo>.
276 Hence, Moo exists as its name -- Minimal Object Orientation -- with a pledge
277 to make it smooth to upgrade to L<Moose> when you need more than minimal
282 If L<Moo> detects L<Moose> being loaded, it will automatically register
283 metaclasses for your L<Moo> and L<Moo::Role> packages, so you should be able
284 to use them in L<Moose> code without anybody ever noticing you aren't using
287 L<Moo> will also create L<Moose type constraints|Moose::Manual::Types> for
288 classes and roles, so that C<< isa => 'MyClass' >> and C<< isa => 'MyRole' >>
289 work the same as for L<Moose> classes and roles.
291 Extending a L<Moose> class or consuming a L<Moose::Role> will also work.
293 So will extending a L<Mouse> class or consuming a L<Mouse::Role> - but note
294 that we don't provide L<Mouse> metaclasses or metaroles so the other way
295 around doesn't work. This feature exists for L<Any::Moose> users porting to
296 L<Moo>; enabling L<Mouse> users to use L<Moo> classes is not a priority for us.
298 This means that there is no need for anything like L<Any::Moose> for Moo
299 code - Moo and Moose code should simply interoperate without problem. To
300 handle L<Mouse> code, you'll likely need an empty Moo role or class consuming
301 or extending the L<Mouse> stuff since it doesn't register true L<Moose>
302 metaclasses like L<Moo> does.
304 If you want types to be upgraded to the L<Moose> types, use
305 L<MooX::Types::MooseLike> and install the L<MooseX::Types> library to
306 match the L<MooX::Types::MooseLike> library you're using - L<Moo> will
307 load the L<MooseX::Types> library and use that type for the newly created
310 If you need to disable the metaclass creation, add:
314 to your code before Moose is loaded, but bear in mind that this switch is
315 currently global and turns the mechanism off entirely so don't put this
318 =head1 MOO VERSUS ANY::MOOSE
320 L<Any::Moose> will load L<Mouse> normally, and L<Moose> in a program using
321 L<Moose> - which theoretically allows you to get the startup time of L<Mouse>
322 without disadvantaging L<Moose> users.
324 Sadly, this doesn't entirely work, since the selection is load order dependent
325 - L<Moo>'s metaclass inflation system explained above in L</MOO AND MOOSE> is
326 significantly more reliable.
328 So if you want to write a CPAN module that loads fast or has only pure perl
329 dependencies but is also fully usable by L<Moose> users, you should be using
332 For a full explanation, see the article
333 L<http://shadow.cat/blog/matt-s-trout/moo-versus-any-moose> which explains
334 the differing strategies in more detail and provides a direct example of
335 where L<Moo> succeeds and L<Any::Moose> fails.
337 =head1 IMPORTED METHODS
341 Foo::Bar->new( attr1 => 3 );
345 Foo::Bar->new({ attr1 => 3 });
350 my ( $class, @args ) = @_;
352 unshift @args, "attr1" if @args % 2 == 1;
359 The default implementation of this method accepts a hash or hash reference of
360 named parameters. If it receives a single argument that isn't a hash reference
363 You can override this method in your class to handle other types of options
364 passed to the constructor.
366 This method should always return a hash reference of named options.
368 =head2 FOREIGNBUILDARGS
370 If you are inheriting from a non-Moo class, the arguments passed to the parent
371 class constructor can be manipulated by defining a C<FOREIGNBUILDARGS> method.
372 It will receive the same arguments as C<BUILDARGS>, and should return a list
373 of arguments to pass to the parent class constructor.
377 Define a C<BUILD> method on your class and the constructor will automatically
378 call the C<BUILD> method from parent down to child after the object has
379 been instantiated. Typically this is used for object validation or possibly
384 If you have a C<DEMOLISH> method anywhere in your inheritance hierarchy,
385 a C<DESTROY> method is created on first object construction which will call
386 C<< $instance->DEMOLISH($in_global_destruction) >> for each C<DEMOLISH>
387 method from child upwards to parents.
389 Note that the C<DESTROY> method is created on first construction of an object
390 of your class in order to not add overhead to classes without C<DEMOLISH>
391 methods; this may prove slightly surprising if you try and define your own.
395 if ($foo->does('Some::Role1')) {
399 Returns true if the object composes in the passed role.
401 =head1 IMPORTED SUBROUTINES
405 extends 'Parent::Class';
407 Declares base class. Multiple superclasses can be passed for multiple
408 inheritance (but please use roles instead).
410 Calling extends more than once will REPLACE your superclasses, not add to
411 them like 'use base' would.
419 with 'Some::Role1', 'Some::Role2';
421 Composes one or more L<Moo::Role> (or L<Role::Tiny>) roles into the current
422 class. An error will be raised if these roles have conflicting methods.
430 Declares an attribute for the class.
442 default => sub { "blah" },
445 Using the C<+> notation, it's possible to override an attribute.
447 The options for C<has> are as follows:
453 B<required>, may be C<ro>, C<lazy>, C<rwp> or C<rw>.
455 C<ro> generates an accessor that dies if you attempt to write to it - i.e.
456 a getter only - by defaulting C<reader> to the name of the attribute.
458 C<lazy> generates a reader like C<ro>, but also sets C<lazy> to 1 and
459 C<builder> to C<_build_${attribute_name}> to allow on-demand generated
460 attributes. This feature was my attempt to fix my incompetence when
461 originally designing C<lazy_build>, and is also implemented by
462 L<MooseX::AttributeShortcuts>. There is, however, nothing to stop you
463 using C<lazy> and C<builder> yourself with C<rwp> or C<rw> - it's just that
464 this isn't generally a good idea so we don't provide a shortcut for it.
466 C<rwp> generates a reader like C<ro>, but also sets C<writer> to
467 C<_set_${attribute_name}> for attributes that are designed to be written
468 from inside of the class, but read-only from outside.
469 This feature comes from L<MooseX::AttributeShortcuts>.
471 C<rw> generates a normal getter/setter by defaulting C<accessor> to the
472 name of the attribute.
476 Takes a coderef which is meant to validate the attribute. Unlike L<Moose>, Moo
477 does not include a basic type system, so instead of doing C<< isa => 'Num' >>,
481 die "$_[0] is not a number!" unless looks_like_number $_[0]
484 Note that the return value is ignored, only whether the sub lives or
487 L<Sub::Quote aware|/SUB QUOTE AWARE>
489 Since L<Moo> does B<not> run the C<isa> check before C<coerce> if a coercion
490 subroutine has been supplied, C<isa> checks are not structural to your code
491 and can, if desired, be omitted on non-debug builds (although if this results
492 in an uncaught bug causing your program to break, the L<Moo> authors guarantee
493 nothing except that you get to keep both halves).
495 If you want L<MooseX::Types> style named types, look at
496 L<MooX::Types::MooseLike>.
498 To cause your C<isa> entries to be automatically mapped to named
499 L<Moose::Meta::TypeConstraint> objects (rather than the default behaviour
500 of creating an anonymous type), set:
502 $Moo::HandleMoose::TYPE_MAP{$isa_coderef} = sub {
503 require MooseX::Types::Something;
504 return MooseX::Types::Something::TypeName();
507 Note that this example is purely illustrative; anything that returns a
508 L<Moose::Meta::TypeConstraint> object or something similar enough to it to
509 make L<Moose> happy is fine.
513 Takes a coderef which is meant to coerce the attribute. The basic idea is to
514 do something like the following:
517 $_[0] + 1 unless $_[0] % 2
520 Note that L<Moo> will always fire your coercion: this is to permit
521 C<isa> entries to be used purely for bug trapping, whereas coercions are
522 always structural to your code. We do, however, apply any supplied C<isa>
523 check after the coercion has run to ensure that it returned a valid value.
525 L<Sub::Quote aware|/SUB QUOTE AWARE>
531 handles => 'RobotRole'
533 Where C<RobotRole> is a role (L<Moo::Role>) that defines an interface which
534 becomes the list of methods to handle.
536 Takes a list of methods
538 handles => [ qw( one two ) ]
548 Takes a coderef which will get called any time the attribute is set. This
549 includes the constructor, but not default or built values. Coderef will be
550 invoked against the object with the new value as an argument.
552 If you set this to just C<1>, it generates a trigger which calls the
553 C<_trigger_${attr_name}> method on C<$self>. This feature comes from
554 L<MooseX::AttributeShortcuts>.
556 Note that Moose also passes the old value, if any; this feature is not yet
559 L<Sub::Quote aware|/SUB QUOTE AWARE>
563 Takes a coderef which will get called with $self as its only argument
564 to populate an attribute if no value is supplied to the constructor - or
565 if the attribute is lazy, when the attribute is first retrieved if no
566 value has yet been provided.
568 If a simple scalar is provided, it will be inlined as a string. Any non-code
569 reference (hash, array) will result in an error - for that case instead use
570 a code reference that returns the desired value.
572 Note that if your default is fired during new() there is no guarantee that
573 other attributes have been populated yet so you should not rely on their
576 L<Sub::Quote aware|/SUB QUOTE AWARE>
580 Takes a method name which will return true if an attribute has a value.
582 If you set this to just C<1>, the predicate is automatically named
583 C<has_${attr_name}> if your attribute's name does not start with an
584 underscore, or C<_has_${attr_name_without_the_underscore}> if it does.
585 This feature comes from L<MooseX::AttributeShortcuts>.
589 Takes a method name which will be called to create the attribute - functions
590 exactly like default except that instead of calling
598 The following features come from L<MooseX::AttributeShortcuts>:
600 If you set this to just C<1>, the builder is automatically named
601 C<_build_${attr_name}>.
603 If you set this to a coderef or code-convertible object, that variable will be
604 installed under C<$class::_build_${attr_name}> and the builder set to the same
609 Takes a method name which will clear the attribute.
611 If you set this to just C<1>, the clearer is automatically named
612 C<clear_${attr_name}> if your attribute's name does not start with an
613 underscore, or <_clear_${attr_name_without_the_underscore}> if it does.
614 This feature comes from L<MooseX::AttributeShortcuts>.
618 B<Boolean>. Set this if you want values for the attribute to be grabbed
619 lazily. This is usually a good idea if you have a L</builder> which requires
620 another attribute to be set.
624 B<Boolean>. Set this if the attribute must be passed on instantiation.
628 The value of this attribute will be the name of the method to get the value of
629 the attribute. If you like Java style methods, you might set this to
634 The value of this attribute will be the name of the method to set the value of
635 the attribute. If you like Java style methods, you might set this to
640 B<Boolean>. Set this if you want the reference that the attribute contains to
641 be weakened; use this when circular references are possible, which will cause
646 Takes the name of the key to look for at instantiation time of the object. A
647 common use of this is to make an underscored attribute have a non-underscored
648 initialization name. C<undef> means that passing the value in on instantiation
653 Takes either a coderef or array of coderefs which is meant to transform the
654 given attributes specifications if necessary when upgrading to a Moose role or
655 class. You shouldn't need this by default, but is provided as a means of
656 possible extensibility.
662 before foo => sub { ... };
664 See L<< Class::Method::Modifiers/before method(s) => sub { ... } >> for full
669 around foo => sub { ... };
671 See L<< Class::Method::Modifiers/around method(s) => sub { ... } >> for full
676 after foo => sub { ... };
678 See L<< Class::Method::Modifiers/after method(s) => sub { ... } >> for full
681 =head1 SUB QUOTE AWARE
683 L<Sub::Quote/quote_sub> allows us to create coderefs that are "inlineable,"
684 giving us a handy, XS-free speed boost. Any option that is L<Sub::Quote>
685 aware can take advantage of this.
687 To do this, you can write
694 isa => quote_sub(q{ die "Not <3" unless $_[0] < 3 })
697 which will be inlined as
700 local @_ = ($_[0]->{foo});
701 die "Not <3" unless $_[0] < 3;
704 or to avoid localizing @_,
708 isa => quote_sub(q{ my ($val) = @_; die "Not <3" unless $val < 3 })
711 which will be inlined as
714 my ($val) = ($_[0]->{foo});
715 die "Not <3" unless $val < 3;
718 See L<Sub::Quote> for more information, including how to pass lexical
719 captures that will also be compiled into the subroutine.
721 =head1 INCOMPATIBILITIES WITH MOOSE
723 There is no built-in type system. C<isa> is verified with a coderef; if you
724 need complex types, just make a library of coderefs, or better yet, functions
725 that return quoted subs. L<MooX::Types::MooseLike> provides a similar API
726 to L<MooseX::Types::Moose> so that you can write
728 has days_to_live => (is => 'ro', isa => Int);
730 and have it work with both; it is hoped that providing only subrefs as an
731 API will encourage the use of other type systems as well, since it's
732 probably the weakest part of Moose design-wise.
734 C<initializer> is not supported in core since the author considers it to be a
735 bad idea and Moose best practices recommend avoiding it. Meanwhile C<trigger> or
736 C<coerce> are more likely to be able to fulfill your needs.
738 There is no meta object. If you need this level of complexity you wanted
739 L<Moose> - Moo succeeds at being small because it explicitly does not
740 provide a metaprotocol. However, if you load L<Moose>, then
742 Class::MOP::class_of($moo_class_or_role)
744 will return an appropriate metaclass pre-populated by L<Moo>.
746 No support for C<super>, C<override>, C<inner>, or C<augment> - the author
747 considers augment to be a bad idea, and override can be translated:
749 override foo => sub {
756 my ($orig, $self) = (shift, shift);
762 The C<dump> method is not provided by default. The author suggests loading
763 L<Devel::Dwarn> into C<main::> (via C<perl -MDevel::Dwarn ...> for example) and
764 using C<$obj-E<gt>$::Dwarn()> instead.
766 L</default> only supports coderefs and plain scalars, because passing a hash
767 or array reference as a default is almost always incorrect since the value is
768 then shared between all objects using that default.
770 C<lazy_build> is not supported; you are instead encouraged to use the
771 C<< is => 'lazy' >> option supported by L<Moo> and L<MooseX::AttributeShortcuts>.
773 C<auto_deref> is not supported since the author considers it a bad idea and
774 it has been considered best practice to avoid it for some time.
776 C<documentation> will show up in a L<Moose> metaclass created from your class
777 but is otherwise ignored. Then again, L<Moose> ignores it as well, so this
778 is arguably not an incompatibility.
780 Since C<coerce> does not require C<isa> to be defined but L<Moose> does
781 require it, the metaclass inflation for coerce alone is a trifle insane
782 and if you attempt to subtype the result will almost certainly break.
784 Handling of warnings: when you C<use Moo> we enable FATAL warnings. The nearest
785 similar invocation for L<Moose> would be:
788 use warnings FATAL => "all";
790 Additionally, L<Moo> supports a set of attribute option shortcuts intended to
791 reduce common boilerplate. The set of shortcuts is the same as in the L<Moose>
792 module L<MooseX::AttributeShortcuts> as of its version 0.009+. So if you:
797 The nearest L<Moose> invocation would be:
802 use warnings FATAL => "all";
803 use MooseX::AttributeShortcuts;
805 or, if you're inheriting from a non-Moose class,
810 use MooseX::NonMoose;
811 use warnings FATAL => "all";
812 use MooseX::AttributeShortcuts;
814 Finally, Moose requires you to call
816 __PACKAGE__->meta->make_immutable;
818 at the end of your class to get an inlined (i.e. not horribly slow)
819 constructor. Moo does it automatically the first time ->new is called
820 on your class. (C<make_immutable> is a no-op in Moo to ease migration.)
822 An extension L<MooX::late> exists to ease translating Moose packages
823 to Moo by providing a more Moose-like interface.
827 Users' IRC: #moose on irc.perl.org
829 =for html <a href="http://chat.mibbit.com/#moose@irc.perl.org">(click for instant chatroom login)</a>
831 Development and contribution IRC: #web-simple on irc.perl.org
833 =for html <a href="http://chat.mibbit.com/#web-simple@irc.perl.org">(click for instant chatroom login)</a>
835 Bugtracker: L<http://rt.cpan.org/NoAuth/Bugs.html?Dist=Moo>
837 Git repository: L<git://git.shadowcat.co.uk/gitmo/Moo.git>
839 Git web access: L<http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=gitmo/Moo.git>
843 mst - Matt S. Trout (cpan:MSTROUT) <mst@shadowcat.co.uk>
847 dg - David Leadbeater (cpan:DGL) <dgl@dgl.cx>
849 frew - Arthur Axel "fREW" Schmidt (cpan:FREW) <frioux@gmail.com>
851 hobbs - Andrew Rodland (cpan:ARODLAND) <arodland@cpan.org>
853 jnap - John Napiorkowski (cpan:JJNAPIORK) <jjn1056@yahoo.com>
855 ribasushi - Peter Rabbitson (cpan:RIBASUSHI) <ribasushi@cpan.org>
857 chip - Chip Salzenberg (cpan:CHIPS) <chip@pobox.com>
859 ajgb - Alex J. G. Burzyński (cpan:AJGB) <ajgb@cpan.org>
861 doy - Jesse Luehrs (cpan:DOY) <doy at tozt dot net>
863 perigrin - Chris Prather (cpan:PERIGRIN) <chris@prather.org>
865 Mithaldu - Christian Walde (cpan:MITHALDU) <walde.christian@googlemail.com>
867 ilmari - Dagfinn Ilmari Mannsåker (cpan:ILMARI) <ilmari@ilmari.org>
869 tobyink - Toby Inkster (cpan:TOBYINK) <tobyink@cpan.org>
871 haarg - Graham Knop (cpan:HAARG) <haarg@cpan.org>
873 mattp - Matt Phillips (cpan:MATTP) <mattp@cpan.org>
877 Copyright (c) 2010-2011 the Moo L</AUTHOR> and L</CONTRIBUTORS>
882 This library is free software and may be distributed under the same terms
883 as perl itself. See L<http://dev.perl.org/licenses/>.