6 our $VERSION = '0.009003'; # 0.9.3
7 $VERSION = eval $VERSION;
15 return if $MAKERS{$target}; # already exported into this package
16 *{_getglob("${target}::extends")} = sub {
17 _load_module($_) for @_;
18 # Can't do *{...} = \@_ or 5.10.0's mro.pm stops seeing @ISA
19 @{*{_getglob("${target}::ISA")}{ARRAY}} = @_;
21 *{_getglob("${target}::with")} = sub {
23 die "Only one role supported at a time by with" if @_ > 1;
24 Moo::Role->apply_role_to_package($target, $_[0]);
26 $MAKERS{$target} = {};
27 *{_getglob("${target}::has")} = sub {
28 my ($name, %spec) = @_;
29 ($MAKERS{$target}{accessor} ||= do {
30 require Method::Generate::Accessor;
31 Method::Generate::Accessor->new
32 })->generate_method($target, $name, \%spec);
33 $class->_constructor_maker_for($target)
34 ->register_attribute_specs($name, \%spec);
36 foreach my $type (qw(before after around)) {
37 *{_getglob "${target}::${type}"} = sub {
38 require Class::Method::Modifiers;
39 _install_modifier($target, $type, @_);
44 @{"${target}::ISA"} = do {
45 require Moo::Object; ('Moo::Object');
46 } unless @{"${target}::ISA"};
50 sub _constructor_maker_for {
51 my ($class, $target) = @_;
52 return unless $MAKERS{$target};
53 $MAKERS{$target}{constructor} ||= do {
54 require Method::Generate::Constructor;
55 Method::Generate::Constructor
58 accessor_generator => do {
59 require Method::Generate::Accessor;
60 Method::Generate::Accessor->new;
64 ->register_attribute_specs(do {
66 # using the -last- entry in @ISA means that classes created by
67 # Role::Tiny as N roles + superclass will still get the attributes
69 if (my $super = do { no strict 'refs'; ${"${target}::ISA"}[-1] }) {
70 if (my $con = $MAKERS{$super}{constructor}) {
71 @spec = %{$con->all_attribute_specs};
83 Moo - Minimalist Object Orientation (with Moose compatiblity)
85 =head1 WARNING WARNING WARNING
87 This is a 0.9 release because we're fairly sure it works. For us. Until it's
88 tested in the wild, we make no guarantees it also works for you.
90 If this module does something unexpected, please submit a failing test.
92 But if it eats your cat, sleeps with your boyfriend, or pushes grandma down
93 the stairs to save her from the terrible secret of space, it's not our fault.
104 my $amount = shift || 1;
106 $self->pounds( $self->pounds - $amount );
116 die "Only SWEET-TREATZ supported!" unless $_[0] eq 'SWEET-TREATZ'
122 isa => quote_sub q{ die "$_[0] is too much cat food!" unless $_[0] < 15 },
129 my $full = Cat::Food->new(
130 taste => 'DELICIOUS.',
131 brand => 'SWEET-TREATZ',
141 This module is an extremely light-weight, high-performance L<Moose> replacement.
142 It also avoids depending on any XS modules to allow simple deployments. The
143 name C<Moo> is based on the idea that it provides almost -but not quite- two
146 Unlike C<Mouse> this module does not aim at full L<Moose> compatibility. See
147 L</INCOMPATIBILITIES> for more details.
149 =head1 WHY MOO EXISTS
151 If you want a full object system with a rich Metaprotocol, L<Moose> is
154 I've tried several times to use L<Mouse> but it's 3x the size of Moo and
155 takes longer to load than most of my Moo based CGI scripts take to run.
157 If you don't want L<Moose>, you don't want "less metaprotocol" like L<Mouse>,
158 you want "as little as possible" - which means "no metaprotocol", which is
161 By Moo 1.0 I intend to have Moo's equivalent of L<Any::Moose> built in -
162 if Moose gets loaded, any Moo class or role will act as a Moose equivalent
165 Hence - Moo exists as its name - Minimal Object Orientation - with a pledge
166 to make it smooth to upgrade to L<Moose> when you need more than minimal
169 =head1 IMPORTED METHODS
173 Foo::Bar->new( attr1 => 3 );
177 Foo::Bar->new({ attr1 => 3 });
181 This feature from Moose is not yet supported.
185 Don't override (or probably even call) this method. Instead, you can define
186 a C<BUILD> method on your class and the constructor will automatically call the
187 C<BUILD> method from parent down to child after the object has been
188 instantiated. Typically this is used for object validation or possibly logging.
192 if ($foo->does('Some::Role1')) {
196 Returns true if the object composes in the passed role.
198 =head1 IMPORTED SUBROUTINES
202 extends 'Parent::Class';
204 Declares base class. Multiple superclasses can be passed for multiple
205 inheritance (but please use roles instead).
207 Calling extends more than once will REPLACE your superclasses, not add to
208 them like 'use base' would.
215 Composes a L<Role::Tiny> into current class. Only one role may be composed in
216 at a time to allow the code to remain as simple as possible.
224 Declares an attribute for the class.
226 The options for C<has> are as follows:
232 B<required>, must be C<ro> or C<rw>. Unsurprisingly, C<ro> generates an
233 accessor that will not respond to arguments; to be clear: a getter only. C<rw>
234 will create a perlish getter/setter.
238 Takes a coderef which is meant to validate the attribute. Unlike L<Moose> Moo
239 does not include a basic type system, so instead of doing C<< isa => 'Num' >>,
243 die "$_[0] is not a number!" unless looks_like_number $_[0]
246 L<Sub::Quote aware|/SUB QUOTE AWARE>
250 This Moose feature is not yet supported
254 Takes a coderef which is meant to coerce the attribute. The basic idea is to
255 do something like the following:
257 coerce => quote_sub q{
258 $_[0] + 1 unless $_[0] % 2
261 L<Sub::Quote aware|/SUB QUOTE AWARE>
267 Takes a coderef which will get called any time the attribute is set. Coderef
268 will be invoked against the object with the new value as an argument.
270 Note that Moose also passes the old value, if any; this feature is not yet
273 L<Sub::Quote aware|/SUB QUOTE AWARE>
277 Takes a coderef which will get called with $self as its only argument
278 to populate an attribute if no value is supplied to the constructor - or
279 if the attribute is lazy, when the attribute is first retrieved if no
280 value has yet been provided.
282 Note that if your default is fired during new() there is no guarantee that
283 other attributes have been populated yet so you should not rely on their
286 L<Sub::Quote aware|/SUB QUOTE AWARE>
290 Takes a method name which will return true if an attribute has a value.
292 A common example of this would be to call it C<has_$foo>, implying that the
293 object has a C<$foo> set.
297 Takes a method name which will be called to create the attribute - functions
298 exactly like default except that instead of calling
308 Takes a method name which will clear the attribute.
312 B<Boolean>. Set this if you want values for the attribute to be grabbed
313 lazily. This is usually a good idea if you have a L</builder> which requires
314 another attribute to be set.
318 B<Boolean>. Set this if the attribute must be passed on instantiation.
322 B<Boolean>. Set this if you want the reference that the attribute contains to
323 be weakened; use this when circular references are possible, which will cause
328 Takes the name of the key to look for at instantiation time of the object. A
329 common use of this is to make an underscored attribute have a non-underscored
330 initialization name. C<undef> means that passing the value in on instantiation
336 before foo => sub { ... };
338 See L<< Class::Method::Modifiers/before method(s) => sub { ... } >> for full
343 around foo => sub { ... };
345 See L<< Class::Method::Modifiers/around method(s) => sub { ... } >> for full
350 after foo => sub { ... };
352 See L<< Class::Method::Modifiers/after method(s) => sub { ... } >> for full
355 =head1 SUB QUOTE AWARE
357 L<Sub::Quote/quote_sub> allows us to create coderefs that are "inlineable,"
358 giving us a handy, XS-free speed boost. Any option that is L<Sub::Quote>
359 aware can take advantage of this.
361 =head1 INCOMPATIBILITIES WITH MOOSE
363 You can only compose one role at a time. If your application is large or
364 complex enough to warrant complex composition, you wanted L<Moose>.
366 There is no complex type system. C<isa> is verified with a coderef, if you
367 need complex types, just make a library of coderefs, or better yet, functions
368 that return quoted subs.
370 C<initializer> is not supported in core since the author considers it to be a
371 bad idea but may be supported by an extension in future.
373 There is no meta object. If you need this level of complexity you wanted
374 L<Moose> - Moo succeeds at being small because it explicitly does not
375 provide a metaprotocol.
377 No support for C<super>, C<override>, C<inner>, or C<augment> - override can
378 be handled by around albeit with a little more typing, and the author considers
379 augment to be a bad idea.
381 L</default> only supports coderefs, because doing otherwise is usually a
384 C<lazy_build> is not supported per se, but of course it will work if you
385 manually set all the options it implies.
387 C<auto_deref> is not supported since the author considers it a bad idea.
389 C<documentation> is not supported since it's a very poor replacement for POD.