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 no warnings 'once'; # piss off. -- mst
97 $Moo::HandleMoose::MOUSE{$target} = [
98 grep defined, map Mouse::Util::find_meta($_), @_
99 ] if Mouse::Util->can('find_meta');
102 sub _maybe_reset_handlemoose {
103 my ($class, $target) = @_;
104 if ($INC{"Moo/HandleMoose.pm"}) {
105 Moo::HandleMoose::maybe_reinject_fake_metaclass_for($target);
109 sub _accessor_maker_for {
110 my ($class, $target) = @_;
111 return unless $MAKERS{$target};
112 $MAKERS{$target}{accessor} ||= do {
113 my $maker_class = do {
115 if (my $defer_target =
116 (Sub::Defer::defer_info($target->can('new'))||[])->[0]
118 my ($pkg) = ($defer_target =~ /^(.*)::[^:]+$/);
119 $MAKERS{$pkg} && $MAKERS{$pkg}{accessor};
126 require Method::Generate::Accessor;
127 'Method::Generate::Accessor'
134 sub _constructor_maker_for {
135 my ($class, $target, $select_super) = @_;
136 return unless $MAKERS{$target};
137 $MAKERS{$target}{constructor} ||= do {
138 require Method::Generate::Constructor;
140 my ($moo_constructor, $con);
142 if ($select_super && $MAKERS{$select_super}) {
143 $moo_constructor = 1;
144 $con = $MAKERS{$select_super}{constructor};
146 my $t_new = $target->can('new');
148 if ($t_new == Moo::Object->can('new')) {
149 $moo_constructor = 1;
150 } elsif (my $defer_target = (Sub::Defer::defer_info($t_new)||[])->[0]) {
151 my ($pkg) = ($defer_target =~ /^(.*)::[^:]+$/);
153 $moo_constructor = 1;
154 $con = $MAKERS{$pkg}{constructor};
158 $moo_constructor = 1; # no other constructor, make a Moo one
161 ($con ? ref($con) : 'Method::Generate::Constructor')
164 accessor_generator => $class->_accessor_maker_for($target),
165 construction_string => (
167 ? ($con ? $con->construction_string : undef)
168 : ('$class->'.$target.'::SUPER::new($class->can(q[FOREIGNBUILDARGS]) ? $class->FOREIGNBUILDARGS(@_) : @_)')
170 subconstructor_handler => (
171 ' if ($Moo::MAKERS{$class}) {'."\n"
172 .' '.$class.'->_constructor_maker_for($class,'.perlstring($target).');'."\n"
173 .' return $class->new(@_)'.";\n"
174 .' } elsif ($INC{"Moose.pm"} and my $meta = Class::MOP::get_metaclass_by_name($class)) {'."\n"
175 .' return $meta->new_object($class->BUILDARGS(@_));'."\n"
180 ->register_attribute_specs(%{$con?$con->all_attribute_specs:{}})
191 Moo - Minimalist Object Orientation (with Moose compatibility)
201 my $amount = shift || 1;
203 $self->pounds( $self->pounds - $amount );
213 die "Only SWEET-TREATZ supported!" unless $_[0] eq 'SWEET-TREATZ'
219 isa => sub { die "$_[0] is too much cat food!" unless $_[0] < 15 },
226 my $full = Cat::Food->new(
227 taste => 'DELICIOUS.',
228 brand => 'SWEET-TREATZ',
238 This module is an extremely light-weight subset of L<Moose> optimised for
239 rapid startup and "pay only for what you use".
241 It also avoids depending on any XS modules to allow simple deployments. The
242 name C<Moo> is based on the idea that it provides almost -- but not quite -- two
245 Unlike L<Mouse> this module does not aim at full compatibility with
246 L<Moose>'s surface syntax, preferring instead of provide full interoperability
247 via the metaclass inflation capabilities described in L</MOO AND MOOSE>.
249 For a full list of the minor differences between L<Moose> and L<Moo>'s surface
250 syntax, see L</INCOMPATIBILITIES WITH MOOSE>.
252 =head1 WHY MOO EXISTS
254 If you want a full object system with a rich Metaprotocol, L<Moose> is
257 However, sometimes you're writing a command line script or a CGI script
258 where fast startup is essential, or code designed to be deployed as a single
259 file via L<App::FatPacker>, or you're writing a CPAN module and you want it
260 to be usable by people with those constraints.
262 I've tried several times to use L<Mouse> but it's 3x the size of Moo and
263 takes longer to load than most of my Moo based CGI scripts take to run.
265 If you don't want L<Moose>, you don't want "less metaprotocol" like L<Mouse>,
266 you want "as little as possible" -- which means "no metaprotocol", which is
269 Better still, if you install and load L<Moose>, we set up metaclasses for your
270 L<Moo> classes and L<Moo::Role> roles, so you can use them in L<Moose> code
271 without ever noticing that some of your codebase is using L<Moo>.
273 Hence, Moo exists as its name -- Minimal Object Orientation -- with a pledge
274 to make it smooth to upgrade to L<Moose> when you need more than minimal
279 If L<Moo> detects L<Moose> being loaded, it will automatically register
280 metaclasses for your L<Moo> and L<Moo::Role> packages, so you should be able
281 to use them in L<Moose> code without anybody ever noticing you aren't using
284 L<Moo> will also create L<Moose type constraints|Moose::Manual::Types> for
285 classes and roles, so that C<< isa => 'MyClass' >> and C<< isa => 'MyRole' >>
286 work the same as for L<Moose> classes and roles.
288 Extending a L<Moose> class or consuming a L<Moose::Role> will also work.
290 So will extending a L<Mouse> class or consuming a L<Mouse::Role> - but note
291 that we don't provide L<Mouse> metaclasses or metaroles so the other way
292 around doesn't work. This feature exists for L<Any::Moose> users porting to
293 L<Moo>; enabling L<Mouse> users to use L<Moo> classes is not a priority for us.
295 This means that there is no need for anything like L<Any::Moose> for Moo
296 code - Moo and Moose code should simply interoperate without problem. To
297 handle L<Mouse> code, you'll likely need an empty Moo role or class consuming
298 or extending the L<Mouse> stuff since it doesn't register true L<Moose>
299 metaclasses like L<Moo> does.
301 If you want types to be upgraded to the L<Moose> types, use
302 L<MooX::Types::MooseLike> and install the L<MooseX::Types> library to
303 match the L<MooX::Types::MooseLike> library you're using - L<Moo> will
304 load the L<MooseX::Types> library and use that type for the newly created
307 If you need to disable the metaclass creation, add:
311 to your code before Moose is loaded, but bear in mind that this switch is
312 currently global and turns the mechanism off entirely so don't put this
315 =head1 MOO VERSUS ANY::MOOSE
317 L<Any::Moose> will load L<Mouse> normally, and L<Moose> in a program using
318 L<Moose> - which theoretically allows you to get the startup time of L<Mouse>
319 without disadvantaging L<Moose> users.
321 Sadly, this doesn't entirely work, since the selection is load order dependent
322 - L<Moo>'s metaclass inflation system explained above in L</MOO AND MOOSE> is
323 significantly more reliable.
325 So if you want to write a CPAN module that loads fast or has only pure perl
326 dependencies but is also fully usable by L<Moose> users, you should be using
329 For a full explanation, see the article
330 L<http://shadow.cat/blog/matt-s-trout/moo-versus-any-moose> which explains
331 the differing strategies in more detail and provides a direct example of
332 where L<Moo> succeeds and L<Any::Moose> fails.
334 =head1 IMPORTED METHODS
338 Foo::Bar->new( attr1 => 3 );
342 Foo::Bar->new({ attr1 => 3 });
347 my ( $class, @args ) = @_;
349 unshift @args, "attr1" if @args % 2 == 1;
356 The default implementation of this method accepts a hash or hash reference of
357 named parameters. If it receives a single argument that isn't a hash reference
360 You can override this method in your class to handle other types of options
361 passed to the constructor.
363 This method should always return a hash reference of named options.
365 =head2 FOREIGNBUILDARGS
367 If you are inheriting from a non-Moo class, the arguments passed to the parent
368 class constructor can be manipulated by defining a C<FOREIGNBUILDARGS> method.
369 It will receive the same arguments as C<BUILDARGS>, and should return a list
370 of arguments to pass to the parent class constructor.
374 Define a C<BUILD> method on your class and the constructor will automatically
375 call the C<BUILD> method from parent down to child after the object has
376 been instantiated. Typically this is used for object validation or possibly
381 If you have a C<DEMOLISH> method anywhere in your inheritance hierarchy,
382 a C<DESTROY> method is created on first object construction which will call
383 C<< $instance->DEMOLISH($in_global_destruction) >> for each C<DEMOLISH>
384 method from child upwards to parents.
386 Note that the C<DESTROY> method is created on first construction of an object
387 of your class in order to not add overhead to classes without C<DEMOLISH>
388 methods; this may prove slightly surprising if you try and define your own.
392 if ($foo->does('Some::Role1')) {
396 Returns true if the object composes in the passed role.
398 =head1 IMPORTED SUBROUTINES
402 extends 'Parent::Class';
404 Declares base class. Multiple superclasses can be passed for multiple
405 inheritance (but please use roles instead).
407 Calling extends more than once will REPLACE your superclasses, not add to
408 them like 'use base' would.
416 with 'Some::Role1', 'Some::Role2';
418 Composes one or more L<Moo::Role> (or L<Role::Tiny>) roles into the current
419 class. An error will be raised if these roles have conflicting methods.
427 Declares an attribute for the class.
439 default => sub { "blah" },
442 Using the C<+> notation, it's possible to override an attribute.
444 The options for C<has> are as follows:
450 B<required>, may be C<ro>, C<lazy>, C<rwp> or C<rw>.
452 C<ro> generates an accessor that dies if you attempt to write to it - i.e.
453 a getter only - by defaulting C<reader> to the name of the attribute.
455 C<lazy> generates a reader like C<ro>, but also sets C<lazy> to 1 and
456 C<builder> to C<_build_${attribute_name}> to allow on-demand generated
457 attributes. This feature was my attempt to fix my incompetence when
458 originally designing C<lazy_build>, and is also implemented by
459 L<MooseX::AttributeShortcuts>. There is, however, nothing to stop you
460 using C<lazy> and C<builder> yourself with C<rwp> or C<rw> - it's just that
461 this isn't generally a good idea so we don't provide a shortcut for it.
463 C<rwp> generates a reader like C<ro>, but also sets C<writer> to
464 C<_set_${attribute_name}> for attributes that are designed to be written
465 from inside of the class, but read-only from outside.
466 This feature comes from L<MooseX::AttributeShortcuts>.
468 C<rw> generates a normal getter/setter by defaulting C<accessor> to the
469 name of the attribute.
473 Takes a coderef which is meant to validate the attribute. Unlike L<Moose>, Moo
474 does not include a basic type system, so instead of doing C<< isa => 'Num' >>,
478 die "$_[0] is not a number!" unless looks_like_number $_[0]
481 Note that the return value is ignored, only whether the sub lives or
484 L<Sub::Quote aware|/SUB QUOTE AWARE>
486 Since L<Moo> does B<not> run the C<isa> check before C<coerce> if a coercion
487 subroutine has been supplied, C<isa> checks are not structural to your code
488 and can, if desired, be omitted on non-debug builds (although if this results
489 in an uncaught bug causing your program to break, the L<Moo> authors guarantee
490 nothing except that you get to keep both halves).
492 If you want L<MooseX::Types> style named types, look at
493 L<MooX::Types::MooseLike>.
495 To cause your C<isa> entries to be automatically mapped to named
496 L<Moose::Meta::TypeConstraint> objects (rather than the default behaviour
497 of creating an anonymous type), set:
499 $Moo::HandleMoose::TYPE_MAP{$isa_coderef} = sub {
500 require MooseX::Types::Something;
501 return MooseX::Types::Something::TypeName();
504 Note that this example is purely illustrative; anything that returns a
505 L<Moose::Meta::TypeConstraint> object or something similar enough to it to
506 make L<Moose> happy is fine.
510 Takes a coderef which is meant to coerce the attribute. The basic idea is to
511 do something like the following:
514 $_[0] + 1 unless $_[0] % 2
517 Note that L<Moo> will always fire your coercion: this is to permit
518 C<isa> entries to be used purely for bug trapping, whereas coercions are
519 always structural to your code. We do, however, apply any supplied C<isa>
520 check after the coercion has run to ensure that it returned a valid value.
522 L<Sub::Quote aware|/SUB QUOTE AWARE>
528 handles => 'RobotRole'
530 Where C<RobotRole> is a role (L<Moo::Role>) that defines an interface which
531 becomes the list of methods to handle.
533 Takes a list of methods
535 handles => [ qw( one two ) ]
545 Takes a coderef which will get called any time the attribute is set. This
546 includes the constructor, but not default or built values. Coderef will be
547 invoked against the object with the new value as an argument.
549 If you set this to just C<1>, it generates a trigger which calls the
550 C<_trigger_${attr_name}> method on C<$self>. This feature comes from
551 L<MooseX::AttributeShortcuts>.
553 Note that Moose also passes the old value, if any; this feature is not yet
556 L<Sub::Quote aware|/SUB QUOTE AWARE>
560 Takes a coderef which will get called with $self as its only argument
561 to populate an attribute if no value is supplied to the constructor - or
562 if the attribute is lazy, when the attribute is first retrieved if no
563 value has yet been provided.
565 If a simple scalar is provided, it will be inlined as a string. Any non-code
566 reference (hash, array) will result in an error - for that case instead use
567 a code reference that returns the desired value.
569 Note that if your default is fired during new() there is no guarantee that
570 other attributes have been populated yet so you should not rely on their
573 L<Sub::Quote aware|/SUB QUOTE AWARE>
577 Takes a method name which will return true if an attribute has a value.
579 If you set this to just C<1>, the predicate is automatically named
580 C<has_${attr_name}> if your attribute's name does not start with an
581 underscore, or C<_has_${attr_name_without_the_underscore}> if it does.
582 This feature comes from L<MooseX::AttributeShortcuts>.
586 Takes a method name which will be called to create the attribute - functions
587 exactly like default except that instead of calling
595 The following features come from L<MooseX::AttributeShortcuts>:
597 If you set this to just C<1>, the builder is automatically named
598 C<_build_${attr_name}>.
600 If you set this to a coderef or code-convertible object, that variable will be
601 installed under C<$class::_build_${attr_name}> and the builder set to the same
606 Takes a method name which will clear the attribute.
608 If you set this to just C<1>, the clearer is automatically named
609 C<clear_${attr_name}> if your attribute's name does not start with an
610 underscore, or <_clear_${attr_name_without_the_underscore}> if it does.
611 This feature comes from L<MooseX::AttributeShortcuts>.
615 B<Boolean>. Set this if you want values for the attribute to be grabbed
616 lazily. This is usually a good idea if you have a L</builder> which requires
617 another attribute to be set.
621 B<Boolean>. Set this if the attribute must be passed on instantiation.
625 The value of this attribute will be the name of the method to get the value of
626 the attribute. If you like Java style methods, you might set this to
631 The value of this attribute will be the name of the method to set the value of
632 the attribute. If you like Java style methods, you might set this to
637 B<Boolean>. Set this if you want the reference that the attribute contains to
638 be weakened; use this when circular references are possible, which will cause
643 Takes the name of the key to look for at instantiation time of the object. A
644 common use of this is to make an underscored attribute have a non-underscored
645 initialization name. C<undef> means that passing the value in on instantiation
650 Takes either a coderef or array of coderefs which is meant to transform the
651 given attributes specifications if necessary when upgrading to a Moose role or
652 class. You shouldn't need this by default, but is provided as a means of
653 possible extensibility.
659 before foo => sub { ... };
661 See L<< Class::Method::Modifiers/before method(s) => sub { ... } >> for full
666 around foo => sub { ... };
668 See L<< Class::Method::Modifiers/around method(s) => sub { ... } >> for full
673 after foo => sub { ... };
675 See L<< Class::Method::Modifiers/after method(s) => sub { ... } >> for full
678 =head1 SUB QUOTE AWARE
680 L<Sub::Quote/quote_sub> allows us to create coderefs that are "inlineable,"
681 giving us a handy, XS-free speed boost. Any option that is L<Sub::Quote>
682 aware can take advantage of this.
684 To do this, you can write
691 isa => quote_sub(q{ die "Not <3" unless $_[0] < 3 })
694 which will be inlined as
697 local @_ = ($_[0]->{foo});
698 die "Not <3" unless $_[0] < 3;
701 or to avoid localizing @_,
705 isa => quote_sub(q{ my ($val) = @_; die "Not <3" unless $val < 3 })
708 which will be inlined as
711 my ($val) = ($_[0]->{foo});
712 die "Not <3" unless $val < 3;
715 See L<Sub::Quote> for more information, including how to pass lexical
716 captures that will also be compiled into the subroutine.
718 =head1 INCOMPATIBILITIES WITH MOOSE
720 There is no built-in type system. C<isa> is verified with a coderef; if you
721 need complex types, just make a library of coderefs, or better yet, functions
722 that return quoted subs. L<MooX::Types::MooseLike> provides a similar API
723 to L<MooseX::Types::Moose> so that you can write
725 has days_to_live => (is => 'ro', isa => Int);
727 and have it work with both; it is hoped that providing only subrefs as an
728 API will encourage the use of other type systems as well, since it's
729 probably the weakest part of Moose design-wise.
731 C<initializer> is not supported in core since the author considers it to be a
732 bad idea and Moose best practices recommend avoiding it. Meanwhile C<trigger> or
733 C<coerce> are more likely to be able to fulfill your needs.
735 There is no meta object. If you need this level of complexity you wanted
736 L<Moose> - Moo succeeds at being small because it explicitly does not
737 provide a metaprotocol. However, if you load L<Moose>, then
739 Class::MOP::class_of($moo_class_or_role)
741 will return an appropriate metaclass pre-populated by L<Moo>.
743 No support for C<super>, C<override>, C<inner>, or C<augment> - the author
744 considers augment to be a bad idea, and override can be translated:
746 override foo => sub {
753 my ($orig, $self) = (shift, shift);
759 The C<dump> method is not provided by default. The author suggests loading
760 L<Devel::Dwarn> into C<main::> (via C<perl -MDevel::Dwarn ...> for example) and
761 using C<$obj-E<gt>$::Dwarn()> instead.
763 L</default> only supports coderefs and plain scalars, because passing a hash
764 or array reference as a default is almost always incorrect since the value is
765 then shared between all objects using that default.
767 C<lazy_build> is not supported; you are instead encouraged to use the
768 C<< is => 'lazy' >> option supported by L<Moo> and L<MooseX::AttributeShortcuts>.
770 C<auto_deref> is not supported since the author considers it a bad idea and
771 it has been considered best practice to avoid it for some time.
773 C<documentation> will show up in a L<Moose> metaclass created from your class
774 but is otherwise ignored. Then again, L<Moose> ignores it as well, so this
775 is arguably not an incompatibility.
777 Since C<coerce> does not require C<isa> to be defined but L<Moose> does
778 require it, the metaclass inflation for coerce alone is a trifle insane
779 and if you attempt to subtype the result will almost certainly break.
781 Handling of warnings: when you C<use Moo> we enable FATAL warnings. The nearest
782 similar invocation for L<Moose> would be:
785 use warnings FATAL => "all";
787 Additionally, L<Moo> supports a set of attribute option shortcuts intended to
788 reduce common boilerplate. The set of shortcuts is the same as in the L<Moose>
789 module L<MooseX::AttributeShortcuts> as of its version 0.009+. So if you:
794 The nearest L<Moose> invocation would be:
799 use warnings FATAL => "all";
800 use MooseX::AttributeShortcuts;
802 or, if you're inheriting from a non-Moose class,
807 use MooseX::NonMoose;
808 use warnings FATAL => "all";
809 use MooseX::AttributeShortcuts;
811 Finally, Moose requires you to call
813 __PACKAGE__->meta->make_immutable;
815 at the end of your class to get an inlined (i.e. not horribly slow)
816 constructor. Moo does it automatically the first time ->new is called
817 on your class. (C<make_immutable> is a no-op in Moo to ease migration.)
819 An extension L<MooX::late> exists to ease translating Moose packages
820 to Moo by providing a more Moose-like interface.
824 Users' IRC: #moose on irc.perl.org
826 =for html <a href="http://chat.mibbit.com/#moose@irc.perl.org">(click for instant chatroom login)</a>
828 Development and contribution IRC: #web-simple on irc.perl.org
830 =for html <a href="http://chat.mibbit.com/#web-simple@irc.perl.org">(click for instant chatroom login)</a>
832 Bugtracker: L<http://rt.cpan.org/NoAuth/Bugs.html?Dist=Moo>
834 Git repository: L<git://git.shadowcat.co.uk/gitmo/Moo.git>
836 Git web access: L<http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=gitmo/Moo.git>
840 mst - Matt S. Trout (cpan:MSTROUT) <mst@shadowcat.co.uk>
844 dg - David Leadbeater (cpan:DGL) <dgl@dgl.cx>
846 frew - Arthur Axel "fREW" Schmidt (cpan:FREW) <frioux@gmail.com>
848 hobbs - Andrew Rodland (cpan:ARODLAND) <arodland@cpan.org>
850 jnap - John Napiorkowski (cpan:JJNAPIORK) <jjn1056@yahoo.com>
852 ribasushi - Peter Rabbitson (cpan:RIBASUSHI) <ribasushi@cpan.org>
854 chip - Chip Salzenberg (cpan:CHIPS) <chip@pobox.com>
856 ajgb - Alex J. G. Burzyński (cpan:AJGB) <ajgb@cpan.org>
858 doy - Jesse Luehrs (cpan:DOY) <doy at tozt dot net>
860 perigrin - Chris Prather (cpan:PERIGRIN) <chris@prather.org>
862 Mithaldu - Christian Walde (cpan:MITHALDU) <walde.christian@googlemail.com>
864 ilmari - Dagfinn Ilmari Mannsåker (cpan:ILMARI) <ilmari@ilmari.org>
866 tobyink - Toby Inkster (cpan:TOBYINK) <tobyink@cpan.org>
868 haarg - Graham Knop (cpan:HAARG) <haarg@cpan.org>
870 mattp - Matt Phillips (cpan:MATTP) <mattp@cpan.org>
874 Copyright (c) 2010-2011 the Moo L</AUTHOR> and L</CONTRIBUTORS>
879 This library is free software and may be distributed under the same terms
880 as perl itself. See L<http://dev.perl.org/licenses/>.