8 our $VERSION = '1.003001';
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 ($Role::Tiny::INFO{$target} and $Role::Tiny::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 = shift;
41 my @name_proto = ref $name_proto eq 'ARRAY' ? @$name_proto : $name_proto;
44 Carp::croak("Invalid options for " . join(', ', map "'$_'", @name_proto)
45 . " attribute(s): even number of arguments expected, got " . scalar @_)
48 foreach my $name (@name_proto) {
49 # Note that when multiple attributes specified, each attribute
50 # needs a separate \%specs hashref
51 my $spec_ref = @name_proto > 1 ? +{%spec} : \%spec;
52 $class->_constructor_maker_for($target)
53 ->register_attribute_specs($name, $spec_ref);
54 $class->_accessor_maker_for($target)
55 ->generate_method($target, $name, $spec_ref);
56 $class->_maybe_reset_handlemoose($target);
60 foreach my $type (qw(before after around)) {
61 _install_tracked $target => $type => sub {
62 require Class::Method::Modifiers;
63 _install_modifier($target, $type, @_);
67 return if $MAKERS{$target}{is_class}; # already exported into this package
68 $MAKERS{$target}{is_class} = 1;
71 @{"${target}::ISA"} = do {
72 require Moo::Object; ('Moo::Object');
73 } unless @{"${target}::ISA"};
75 if ($INC{'Moo/HandleMoose.pm'}) {
76 Moo::HandleMoose::inject_fake_metaclass_for($target);
82 _unimport_coderefs($target, $MAKERS{$target});
85 sub _set_superclasses {
88 foreach my $superclass (@_) {
89 _load_module($superclass);
90 if ($INC{"Role/Tiny.pm"} && $Role::Tiny::INFO{$superclass}) {
92 Carp::croak("Can't extend role '$superclass'");
95 # Can't do *{...} = \@_ or 5.10.0's mro.pm stops seeing @ISA
96 @{*{_getglob("${target}::ISA")}{ARRAY}} = @_;
97 if (my $old = delete $Moo::MAKERS{$target}{constructor}) {
98 delete _getstash($target)->{new};
99 Moo->_constructor_maker_for($target)
100 ->register_attribute_specs(%{$old->all_attribute_specs});
102 elsif (!$target->isa('Moo::Object')) {
103 Moo->_constructor_maker_for($target);
105 no warnings 'once'; # piss off. -- mst
106 $Moo::HandleMoose::MOUSE{$target} = [
107 grep defined, map Mouse::Util::find_meta($_), @_
108 ] if Mouse::Util->can('find_meta');
111 sub _maybe_reset_handlemoose {
112 my ($class, $target) = @_;
113 if ($INC{"Moo/HandleMoose.pm"}) {
114 Moo::HandleMoose::maybe_reinject_fake_metaclass_for($target);
118 sub _accessor_maker_for {
119 my ($class, $target) = @_;
120 return unless $MAKERS{$target};
121 $MAKERS{$target}{accessor} ||= do {
122 my $maker_class = do {
124 if (my $defer_target =
125 (Sub::Defer::defer_info($target->can('new'))||[])->[0]
127 my ($pkg) = ($defer_target =~ /^(.*)::[^:]+$/);
128 $MAKERS{$pkg} && $MAKERS{$pkg}{accessor};
135 require Method::Generate::Accessor;
136 'Method::Generate::Accessor'
143 sub _constructor_maker_for {
144 my ($class, $target, $select_super) = @_;
145 return unless $MAKERS{$target};
146 $MAKERS{$target}{constructor} ||= do {
147 require Method::Generate::Constructor;
149 my ($moo_constructor, $con);
151 if ($select_super && $MAKERS{$select_super}) {
152 $moo_constructor = 1;
153 $con = $MAKERS{$select_super}{constructor};
155 my $t_new = $target->can('new');
157 if ($t_new == Moo::Object->can('new')) {
158 $moo_constructor = 1;
159 } elsif (my $defer_target = (Sub::Defer::defer_info($t_new)||[])->[0]) {
160 my ($pkg) = ($defer_target =~ /^(.*)::[^:]+$/);
162 $moo_constructor = 1;
163 $con = $MAKERS{$pkg}{constructor};
167 $moo_constructor = 1; # no other constructor, make a Moo one
170 ($con ? ref($con) : 'Method::Generate::Constructor')
173 accessor_generator => $class->_accessor_maker_for($target),
174 construction_string => (
176 ? ($con ? $con->construction_string : undef)
177 : ('$class->'.$target.'::SUPER::new($class->can(q[FOREIGNBUILDARGS]) ? $class->FOREIGNBUILDARGS(@_) : @_)')
179 subconstructor_handler => (
180 ' if ($Moo::MAKERS{$class}) {'."\n"
181 .' '.$class.'->_constructor_maker_for($class,'.perlstring($target).');'."\n"
182 .' return $class->new(@_)'.";\n"
183 .' } elsif ($INC{"Moose.pm"} and my $meta = Class::MOP::get_metaclass_by_name($class)) {'."\n"
184 .' return $meta->new_object($class->BUILDARGS(@_));'."\n"
189 ->register_attribute_specs(%{$con?$con->all_attribute_specs:{}})
202 Moo - Minimalist Object Orientation (with Moose compatibility)
212 my $amount = shift || 1;
214 $self->pounds( $self->pounds - $amount );
224 die "Only SWEET-TREATZ supported!" unless $_[0] eq 'SWEET-TREATZ'
230 isa => sub { die "$_[0] is too much cat food!" unless $_[0] < 15 },
237 my $full = Cat::Food->new(
238 taste => 'DELICIOUS.',
239 brand => 'SWEET-TREATZ',
249 This module is an extremely light-weight subset of L<Moose> optimised for
250 rapid startup and "pay only for what you use".
252 It also avoids depending on any XS modules to allow simple deployments. The
253 name C<Moo> is based on the idea that it provides almost -- but not quite -- two
256 Unlike L<Mouse> this module does not aim at full compatibility with
257 L<Moose>'s surface syntax, preferring instead of provide full interoperability
258 via the metaclass inflation capabilities described in L</MOO AND MOOSE>.
260 For a full list of the minor differences between L<Moose> and L<Moo>'s surface
261 syntax, see L</INCOMPATIBILITIES WITH MOOSE>.
263 =head1 WHY MOO EXISTS
265 If you want a full object system with a rich Metaprotocol, L<Moose> is
268 However, sometimes you're writing a command line script or a CGI script
269 where fast startup is essential, or code designed to be deployed as a single
270 file via L<App::FatPacker>, or you're writing a CPAN module and you want it
271 to be usable by people with those constraints.
273 I've tried several times to use L<Mouse> but it's 3x the size of Moo and
274 takes longer to load than most of my Moo based CGI scripts take to run.
276 If you don't want L<Moose>, you don't want "less metaprotocol" like L<Mouse>,
277 you want "as little as possible" -- which means "no metaprotocol", which is
280 Better still, if you install and load L<Moose>, we set up metaclasses for your
281 L<Moo> classes and L<Moo::Role> roles, so you can use them in L<Moose> code
282 without ever noticing that some of your codebase is using L<Moo>.
284 Hence, Moo exists as its name -- Minimal Object Orientation -- with a pledge
285 to make it smooth to upgrade to L<Moose> when you need more than minimal
290 If L<Moo> detects L<Moose> being loaded, it will automatically register
291 metaclasses for your L<Moo> and L<Moo::Role> packages, so you should be able
292 to use them in L<Moose> code without anybody ever noticing you aren't using
295 L<Moo> will also create L<Moose type constraints|Moose::Manual::Types> for
296 classes and roles, so that C<< isa => 'MyClass' >> and C<< isa => 'MyRole' >>
297 work the same as for L<Moose> classes and roles.
299 Extending a L<Moose> class or consuming a L<Moose::Role> will also work.
301 So will extending a L<Mouse> class or consuming a L<Mouse::Role> - but note
302 that we don't provide L<Mouse> metaclasses or metaroles so the other way
303 around doesn't work. This feature exists for L<Any::Moose> users porting to
304 L<Moo>; enabling L<Mouse> users to use L<Moo> classes is not a priority for us.
306 This means that there is no need for anything like L<Any::Moose> for Moo
307 code - Moo and Moose code should simply interoperate without problem. To
308 handle L<Mouse> code, you'll likely need an empty Moo role or class consuming
309 or extending the L<Mouse> stuff since it doesn't register true L<Moose>
310 metaclasses like L<Moo> does.
312 If you want types to be upgraded to the L<Moose> types, use
313 L<MooX::Types::MooseLike> and install the L<MooseX::Types> library to
314 match the L<MooX::Types::MooseLike> library you're using - L<Moo> will
315 load the L<MooseX::Types> library and use that type for the newly created
318 If you need to disable the metaclass creation, add:
322 to your code before Moose is loaded, but bear in mind that this switch is
323 currently global and turns the mechanism off entirely so don't put this
326 =head1 MOO AND CLASS::XSACCESSOR
328 If a new enough version of L<Class::XSAccessor> is available, it
329 will be used to generate simple accessors, readers, and writers for
330 a speed boost. Simple accessors are those without lazy defaults,
331 type checks/coercions, or triggers. Readers and writers generated
332 by L<Class::XSAccessor> will behave slightly differently: they will
333 reject attempts to call them with the incorrect number of parameters.
335 =head1 MOO VERSUS ANY::MOOSE
337 L<Any::Moose> will load L<Mouse> normally, and L<Moose> in a program using
338 L<Moose> - which theoretically allows you to get the startup time of L<Mouse>
339 without disadvantaging L<Moose> users.
341 Sadly, this doesn't entirely work, since the selection is load order dependent
342 - L<Moo>'s metaclass inflation system explained above in L</MOO AND MOOSE> is
343 significantly more reliable.
345 So if you want to write a CPAN module that loads fast or has only pure perl
346 dependencies but is also fully usable by L<Moose> users, you should be using
349 For a full explanation, see the article
350 L<http://shadow.cat/blog/matt-s-trout/moo-versus-any-moose> which explains
351 the differing strategies in more detail and provides a direct example of
352 where L<Moo> succeeds and L<Any::Moose> fails.
354 =head1 IMPORTED METHODS
358 Foo::Bar->new( attr1 => 3 );
362 Foo::Bar->new({ attr1 => 3 });
367 my ( $class, @args ) = @_;
369 unshift @args, "attr1" if @args % 2 == 1;
376 The default implementation of this method accepts a hash or hash reference of
377 named parameters. If it receives a single argument that isn't a hash reference
380 You can override this method in your class to handle other types of options
381 passed to the constructor.
383 This method should always return a hash reference of named options.
385 =head2 FOREIGNBUILDARGS
387 If you are inheriting from a non-Moo class, the arguments passed to the parent
388 class constructor can be manipulated by defining a C<FOREIGNBUILDARGS> method.
389 It will receive the same arguments as C<BUILDARGS>, and should return a list
390 of arguments to pass to the parent class constructor.
394 Define a C<BUILD> method on your class and the constructor will automatically
395 call the C<BUILD> method from parent down to child after the object has
396 been instantiated. Typically this is used for object validation or possibly
401 If you have a C<DEMOLISH> method anywhere in your inheritance hierarchy,
402 a C<DESTROY> method is created on first object construction which will call
403 C<< $instance->DEMOLISH($in_global_destruction) >> for each C<DEMOLISH>
404 method from child upwards to parents.
406 Note that the C<DESTROY> method is created on first construction of an object
407 of your class in order to not add overhead to classes without C<DEMOLISH>
408 methods; this may prove slightly surprising if you try and define your own.
412 if ($foo->does('Some::Role1')) {
416 Returns true if the object composes in the passed role.
418 =head1 IMPORTED SUBROUTINES
422 extends 'Parent::Class';
424 Declares base class. Multiple superclasses can be passed for multiple
425 inheritance (but please use roles instead).
427 Calling extends more than once will REPLACE your superclasses, not add to
428 them like 'use base' would.
436 with 'Some::Role1', 'Some::Role2';
438 Composes one or more L<Moo::Role> (or L<Role::Tiny>) roles into the current
439 class. An error will be raised if these roles have conflicting methods.
447 Declares an attribute for the class.
459 default => sub { "blah" },
462 Using the C<+> notation, it's possible to override an attribute.
464 The options for C<has> are as follows:
470 B<required>, may be C<ro>, C<lazy>, C<rwp> or C<rw>.
472 C<ro> generates an accessor that dies if you attempt to write to it - i.e.
473 a getter only - by defaulting C<reader> to the name of the attribute.
475 C<lazy> generates a reader like C<ro>, but also sets C<lazy> to 1 and
476 C<builder> to C<_build_${attribute_name}> to allow on-demand generated
477 attributes. This feature was my attempt to fix my incompetence when
478 originally designing C<lazy_build>, and is also implemented by
479 L<MooseX::AttributeShortcuts>. There is, however, nothing to stop you
480 using C<lazy> and C<builder> yourself with C<rwp> or C<rw> - it's just that
481 this isn't generally a good idea so we don't provide a shortcut for it.
483 C<rwp> generates a reader like C<ro>, but also sets C<writer> to
484 C<_set_${attribute_name}> for attributes that are designed to be written
485 from inside of the class, but read-only from outside.
486 This feature comes from L<MooseX::AttributeShortcuts>.
488 C<rw> generates a normal getter/setter by defaulting C<accessor> to the
489 name of the attribute.
493 Takes a coderef which is meant to validate the attribute. Unlike L<Moose>, Moo
494 does not include a basic type system, so instead of doing C<< isa => 'Num' >>,
498 die "$_[0] is not a number!" unless looks_like_number $_[0]
501 Note that the return value is ignored, only whether the sub lives or
504 L<Sub::Quote aware|/SUB QUOTE AWARE>
506 Since L<Moo> does B<not> run the C<isa> check before C<coerce> if a coercion
507 subroutine has been supplied, C<isa> checks are not structural to your code
508 and can, if desired, be omitted on non-debug builds (although if this results
509 in an uncaught bug causing your program to break, the L<Moo> authors guarantee
510 nothing except that you get to keep both halves).
512 If you want L<MooseX::Types> style named types, look at
513 L<MooX::Types::MooseLike>.
515 To cause your C<isa> entries to be automatically mapped to named
516 L<Moose::Meta::TypeConstraint> objects (rather than the default behaviour
517 of creating an anonymous type), set:
519 $Moo::HandleMoose::TYPE_MAP{$isa_coderef} = sub {
520 require MooseX::Types::Something;
521 return MooseX::Types::Something::TypeName();
524 Note that this example is purely illustrative; anything that returns a
525 L<Moose::Meta::TypeConstraint> object or something similar enough to it to
526 make L<Moose> happy is fine.
530 Takes a coderef which is meant to coerce the attribute. The basic idea is to
531 do something like the following:
534 $_[0] % 2 ? $_[0] : $_[0] + 1
537 Note that L<Moo> will always fire your coercion: this is to permit
538 C<isa> entries to be used purely for bug trapping, whereas coercions are
539 always structural to your code. We do, however, apply any supplied C<isa>
540 check after the coercion has run to ensure that it returned a valid value.
542 L<Sub::Quote aware|/SUB QUOTE AWARE>
548 handles => 'RobotRole'
550 Where C<RobotRole> is a role (L<Moo::Role>) that defines an interface which
551 becomes the list of methods to handle.
553 Takes a list of methods
555 handles => [ qw( one two ) ]
565 Takes a coderef which will get called any time the attribute is set. This
566 includes the constructor, but not default or built values. Coderef will be
567 invoked against the object with the new value as an argument.
569 If you set this to just C<1>, it generates a trigger which calls the
570 C<_trigger_${attr_name}> method on C<$self>. This feature comes from
571 L<MooseX::AttributeShortcuts>.
573 Note that Moose also passes the old value, if any; this feature is not yet
576 L<Sub::Quote aware|/SUB QUOTE AWARE>
580 Takes a coderef which will get called with $self as its only argument
581 to populate an attribute if no value is supplied to the constructor - or
582 if the attribute is lazy, when the attribute is first retrieved if no
583 value has yet been provided.
585 If a simple scalar is provided, it will be inlined as a string. Any non-code
586 reference (hash, array) will result in an error - for that case instead use
587 a code reference that returns the desired value.
589 Note that if your default is fired during new() there is no guarantee that
590 other attributes have been populated yet so you should not rely on their
593 L<Sub::Quote aware|/SUB QUOTE AWARE>
597 Takes a method name which will return true if an attribute has a value.
599 If you set this to just C<1>, the predicate is automatically named
600 C<has_${attr_name}> if your attribute's name does not start with an
601 underscore, or C<_has_${attr_name_without_the_underscore}> if it does.
602 This feature comes from L<MooseX::AttributeShortcuts>.
606 Takes a method name which will be called to create the attribute - functions
607 exactly like default except that instead of calling
615 The following features come from L<MooseX::AttributeShortcuts>:
617 If you set this to just C<1>, the builder is automatically named
618 C<_build_${attr_name}>.
620 If you set this to a coderef or code-convertible object, that variable will be
621 installed under C<$class::_build_${attr_name}> and the builder set to the same
626 Takes a method name which will clear the attribute.
628 If you set this to just C<1>, the clearer is automatically named
629 C<clear_${attr_name}> if your attribute's name does not start with an
630 underscore, or <_clear_${attr_name_without_the_underscore}> if it does.
631 This feature comes from L<MooseX::AttributeShortcuts>.
635 B<Boolean>. Set this if you want values for the attribute to be grabbed
636 lazily. This is usually a good idea if you have a L</builder> which requires
637 another attribute to be set.
641 B<Boolean>. Set this if the attribute must be passed on instantiation.
645 The value of this attribute will be the name of the method to get the value of
646 the attribute. If you like Java style methods, you might set this to
651 The value of this attribute will be the name of the method to set the value of
652 the attribute. If you like Java style methods, you might set this to
657 B<Boolean>. Set this if you want the reference that the attribute contains to
658 be weakened; use this when circular references are possible, which will cause
663 Takes the name of the key to look for at instantiation time of the object. A
664 common use of this is to make an underscored attribute have a non-underscored
665 initialization name. C<undef> means that passing the value in on instantiation
670 Takes either a coderef or array of coderefs which is meant to transform the
671 given attributes specifications if necessary when upgrading to a Moose role or
672 class. You shouldn't need this by default, but is provided as a means of
673 possible extensibility.
679 before foo => sub { ... };
681 See L<< Class::Method::Modifiers/before method(s) => sub { ... } >> for full
686 around foo => sub { ... };
688 See L<< Class::Method::Modifiers/around method(s) => sub { ... } >> for full
693 after foo => sub { ... };
695 See L<< Class::Method::Modifiers/after method(s) => sub { ... } >> for full
698 =head1 SUB QUOTE AWARE
700 L<Sub::Quote/quote_sub> allows us to create coderefs that are "inlineable,"
701 giving us a handy, XS-free speed boost. Any option that is L<Sub::Quote>
702 aware can take advantage of this.
704 To do this, you can write
711 isa => quote_sub(q{ die "Not <3" unless $_[0] < 3 })
714 which will be inlined as
717 local @_ = ($_[0]->{foo});
718 die "Not <3" unless $_[0] < 3;
721 or to avoid localizing @_,
725 isa => quote_sub(q{ my ($val) = @_; die "Not <3" unless $val < 3 })
728 which will be inlined as
731 my ($val) = ($_[0]->{foo});
732 die "Not <3" unless $val < 3;
735 See L<Sub::Quote> for more information, including how to pass lexical
736 captures that will also be compiled into the subroutine.
738 =head1 INCOMPATIBILITIES WITH MOOSE
740 There is no built-in type system. C<isa> is verified with a coderef; if you
741 need complex types, just make a library of coderefs, or better yet, functions
742 that return quoted subs. L<MooX::Types::MooseLike> provides a similar API
743 to L<MooseX::Types::Moose> so that you can write
745 has days_to_live => (is => 'ro', isa => Int);
747 and have it work with both; it is hoped that providing only subrefs as an
748 API will encourage the use of other type systems as well, since it's
749 probably the weakest part of Moose design-wise.
751 C<initializer> is not supported in core since the author considers it to be a
752 bad idea and Moose best practices recommend avoiding it. Meanwhile C<trigger> or
753 C<coerce> are more likely to be able to fulfill your needs.
755 There is no meta object. If you need this level of complexity you wanted
756 L<Moose> - Moo succeeds at being small because it explicitly does not
757 provide a metaprotocol. However, if you load L<Moose>, then
759 Class::MOP::class_of($moo_class_or_role)
761 will return an appropriate metaclass pre-populated by L<Moo>.
763 No support for C<super>, C<override>, C<inner>, or C<augment> - the author
764 considers augment to be a bad idea, and override can be translated:
766 override foo => sub {
773 my ($orig, $self) = (shift, shift);
779 The C<dump> method is not provided by default. The author suggests loading
780 L<Devel::Dwarn> into C<main::> (via C<perl -MDevel::Dwarn ...> for example) and
781 using C<$obj-E<gt>$::Dwarn()> instead.
783 L</default> only supports coderefs and plain scalars, because passing a hash
784 or array reference as a default is almost always incorrect since the value is
785 then shared between all objects using that default.
787 C<lazy_build> is not supported; you are instead encouraged to use the
788 C<< is => 'lazy' >> option supported by L<Moo> and L<MooseX::AttributeShortcuts>.
790 C<auto_deref> is not supported since the author considers it a bad idea and
791 it has been considered best practice to avoid it for some time.
793 C<documentation> will show up in a L<Moose> metaclass created from your class
794 but is otherwise ignored. Then again, L<Moose> ignores it as well, so this
795 is arguably not an incompatibility.
797 Since C<coerce> does not require C<isa> to be defined but L<Moose> does
798 require it, the metaclass inflation for coerce alone is a trifle insane
799 and if you attempt to subtype the result will almost certainly break.
801 Handling of warnings: when you C<use Moo> we enable FATAL warnings. The nearest
802 similar invocation for L<Moose> would be:
805 use warnings FATAL => "all";
807 Additionally, L<Moo> supports a set of attribute option shortcuts intended to
808 reduce common boilerplate. The set of shortcuts is the same as in the L<Moose>
809 module L<MooseX::AttributeShortcuts> as of its version 0.009+. So if you:
814 The nearest L<Moose> invocation would be:
819 use warnings FATAL => "all";
820 use MooseX::AttributeShortcuts;
822 or, if you're inheriting from a non-Moose class,
827 use MooseX::NonMoose;
828 use warnings FATAL => "all";
829 use MooseX::AttributeShortcuts;
831 Finally, Moose requires you to call
833 __PACKAGE__->meta->make_immutable;
835 at the end of your class to get an inlined (i.e. not horribly slow)
836 constructor. Moo does it automatically the first time ->new is called
837 on your class. (C<make_immutable> is a no-op in Moo to ease migration.)
839 An extension L<MooX::late> exists to ease translating Moose packages
840 to Moo by providing a more Moose-like interface.
844 Users' IRC: #moose on irc.perl.org
846 =for html <a href="http://chat.mibbit.com/#moose@irc.perl.org">(click for instant chatroom login)</a>
848 Development and contribution IRC: #web-simple on irc.perl.org
850 =for html <a href="http://chat.mibbit.com/#web-simple@irc.perl.org">(click for instant chatroom login)</a>
852 Bugtracker: L<http://rt.cpan.org/NoAuth/Bugs.html?Dist=Moo>
854 Git repository: L<git://git.shadowcat.co.uk/gitmo/Moo.git>
856 Git web access: L<http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=gitmo/Moo.git>
860 mst - Matt S. Trout (cpan:MSTROUT) <mst@shadowcat.co.uk>
864 dg - David Leadbeater (cpan:DGL) <dgl@dgl.cx>
866 frew - Arthur Axel "fREW" Schmidt (cpan:FREW) <frioux@gmail.com>
868 hobbs - Andrew Rodland (cpan:ARODLAND) <arodland@cpan.org>
870 jnap - John Napiorkowski (cpan:JJNAPIORK) <jjn1056@yahoo.com>
872 ribasushi - Peter Rabbitson (cpan:RIBASUSHI) <ribasushi@cpan.org>
874 chip - Chip Salzenberg (cpan:CHIPS) <chip@pobox.com>
876 ajgb - Alex J. G. Burzyński (cpan:AJGB) <ajgb@cpan.org>
878 doy - Jesse Luehrs (cpan:DOY) <doy at tozt dot net>
880 perigrin - Chris Prather (cpan:PERIGRIN) <chris@prather.org>
882 Mithaldu - Christian Walde (cpan:MITHALDU) <walde.christian@googlemail.com>
884 ilmari - Dagfinn Ilmari Mannsåker (cpan:ILMARI) <ilmari@ilmari.org>
886 tobyink - Toby Inkster (cpan:TOBYINK) <tobyink@cpan.org>
888 haarg - Graham Knop (cpan:HAARG) <haarg@cpan.org>
890 mattp - Matt Phillips (cpan:MATTP) <mattp@cpan.org>
894 Copyright (c) 2010-2011 the Moo L</AUTHOR> and L</CONTRIBUTORS>
899 This library is free software and may be distributed under the same terms
900 as perl itself. See L<http://dev.perl.org/licenses/>.