1;
-and else where
+And elsewhere:
my $full = Cat::Food->new(
taste => 'DELICIOUS.',
=head1 DESCRIPTION
This module is an extremely light-weight subset of L<Moose> optimised for
-rapid startup and pay for what you use.
+rapid startup and "pay only for what you use".
It also avoids depending on any XS modules to allow simple deployments. The
-name C<Moo> is based on the idea that it provides almost -but not quite- two
+name C<Moo> is based on the idea that it provides almost -- but not quite -- two
thirds of L<Moose>.
-Unlike C<Mouse> this module does not aim at full compatibility with
+Unlike L<Mouse> this module does not aim at full compatibility with
L<Moose>'s surface syntax, preferring instead of provide full interoperability
via the metaclass inflation capabilites described in L</MOO AND MOOSE>.
takes longer to load than most of my Moo based CGI scripts take to run.
If you don't want L<Moose>, you don't want "less metaprotocol" like L<Mouse>,
-you want "as little as possible" - which means "no metaprotocol", which is
+you want "as little as possible" -- which means "no metaprotocol", which is
what Moo provides.
Better still, if you install and load L<Moose>, we set up metaclasses for your
L<Moo> classes and L<Moo::Role> roles, so you can use them in L<Moose> code
without ever noticing that some of your codebase is using L<Moo>.
-Hence - Moo exists as its name - Minimal Object Orientation - with a pledge
+Hence, Moo exists as its name -- Minimal Object Orientation -- with a pledge
to make it smooth to upgrade to L<Moose> when you need more than minimal
features.
So will extending a L<Mouse> class or consuming a L<Mouse::Role> - but note
that we don't provide L<Mouse> metaclasses or metaroles so the other way
around doesn't work. This feature exists for L<Any::Moose> users porting to
-L<Moo>, enabling L<Mouse> users to use L<Moo> classes is not a priority for us.
+L<Moo>; enabling L<Mouse> users to use L<Moo> classes is not a priority for us.
This means that there is no need for anything like L<Any::Moose> for Moo
code - Moo and Moose code should simply interoperate without problem. To
=item * isa
-Takes a coderef which is meant to validate the attribute. Unlike L<Moose> Moo
+Takes a coderef which is meant to validate the attribute. Unlike L<Moose>, Moo
does not include a basic type system, so instead of doing C<< isa => 'Num' >>,
one should do
$_[0] + 1 unless $_[0] % 2
},
-Note that L<Moo> will always fire your coercion - this is to permit
-isa entries to be used purely for bug trapping, whereas coercions are
+Note that L<Moo> will always fire your coercion: this is to permit
+C<isa> entries to be used purely for bug trapping, whereas coercions are
always structural to your code. We do, however, apply any supplied C<isa>
check after the coercion has run to ensure that it returned a valid value.
L<Sub::Quote aware|/SUB QUOTE AWARE>
-=item * default
+=item * C<default>
Takes a coderef which will get called with $self as its only argument
to populate an attribute if no value is supplied to the constructor - or
L<Sub::Quote aware|/SUB QUOTE AWARE>
-=item * predicate
+=item * C<predicate>
Takes a method name which will return true if an attribute has a value.
underscore, or <_has_${attr_name_without_the_underscore}> if it does.
This feature comes from L<MooseX::AttributeShortcuts>.
-=item * builder
+=item * C<builder>
Takes a method name which will be called to create the attribute - functions
exactly like default except that instead of calling
If you set this to just C<1>, the predicate is automatically named
C<_build_${attr_name}>. This feature comes from L<MooseX::AttributeShortcuts>.
-=item * clearer
+=item * C<clearer>
Takes a method name which will clear the attribute.
underscore, or <_clear_${attr_name_without_the_underscore}> if it does.
This feature comes from L<MooseX::AttributeShortcuts>.
-=item * lazy
+=item * C<lazy>
B<Boolean>. Set this if you want values for the attribute to be grabbed
lazily. This is usually a good idea if you have a L</builder> which requires
another attribute to be set.
-=item * required
+=item * C<required>
B<Boolean>. Set this if the attribute must be passed on instantiation.
-=item * reader
+=item * C<reader>
The value of this attribute will be the name of the method to get the value of
the attribute. If you like Java style methods, you might set this to
C<get_foo>
-=item * writer
+=item * C<writer>
The value of this attribute will be the name of the method to set the value of
the attribute. If you like Java style methods, you might set this to
-C<set_foo>
+C<set_foo>.
-=item * weak_ref
+=item * C<weak_ref>
B<Boolean>. Set this if you want the reference that the attribute contains to
be weakened; use this when circular references are possible, which will cause
leaks.
-=item * init_arg
+=item * C<init_arg>
Takes the name of the key to look for at instantiation time of the object. A
common use of this is to make an underscored attribute have a non-underscored
}
See L<Sub::Quote> for more information, including how to pass lexical
-captures that will also be compiled in to the subroutine.
+captures that will also be compiled into the subroutine.
=head1 INCOMPATIBILITIES WITH MOOSE
-There is no built in type system. C<isa> is verified with a coderef, if you
+There is no built-in type system. C<isa> is verified with a coderef; if you
need complex types, just make a library of coderefs, or better yet, functions
that return quoted subs. L<MooX::Types::MooseLike> provides a similar API
to L<MooseX::Types::Moose> so that you can write
mistake anyway.
C<lazy_build> is not supported; you are instead encouraged to use the
-C<is => 'lazy'> option supported by L<Moo> and L<MooseX::AttributeShortcuts>.
+C<< is => 'lazy' >> option supported by L<Moo> and L<MooseX::AttributeShortcuts>.
C<auto_deref> is not supported since the author considers it a bad idea.
is arguably not an incompatibility.
Since C<coerce> does not require C<isa> to be defined but L<Moose> does
-require it, the metaclass inflation for coerce-alone is a trifle insane
+require it, the metaclass inflation for coerce alone is a trifle insane
and if you attempt to subtype the result will almost certainly break.
Handling of warnings: when you C<use Moo> we enable FATAL warnings. The nearest
projects / gitmo/Moo.git / commitdiff