DESCRIPTION

This module is an extremely light-weight, high-performance Moose replacement. It also avoids depending on any XS modules to allow simple deployments. The name Moo is based on the idea that it provides almost -but not quite- two thirds of Moose.

WHY MOO EXISTS

If you want a full object system with a rich Metaprotocol, Moose is already wonderful.

I've tried several times to use Mouse but it's 3x the size of Moo and takes longer to load than most of my Moo based CGI scripts take to run.

If you don't want Moose, you don't want "less metaprotocol" like Mouse, you want "as little as possible" - which means "no metaprotocol", which is what Moo provides.

By Moo 1.0 I intend to have Moo's equivalent of Any::Moose built in - if Moose gets loaded, any Moo class or role will act as a Moose equivalent if treated as such.

Hence - Moo exists as its name - Minimal Object Orientation - with a pledge to make it smooth to upgrade to Moose when you need more than minimal features.

Moo and Moose - NEW, EXPERIMENTAL

If Moo detects Moose being loaded, it will automatically register metaclasses for your Moo and Moo::Role packages, so you should be able to use them in Moose code without it ever realising you aren't using Moose everywhere.

This means that there is no need for anything like Any::Moose for Moo code - Moo and Moose code should simply interoperate without problem.

However, these features are new as of 0.91.0 (0.091000) so while serviceable, they are absolutely certain to not be 100% yet; please do report bugs.

If you need to disable the metaclass creation, add:

no Moo::sification;

to your code before Moose is loaded, but bear in mind that this switch is currently global and turns the mechanism off entirely, so don't put this in library code, only in a top level script as a temporary measure while you send a bug report.

IMPORTED METHODS

new

BUILDARGS

The default implementation of this method accepts a hash or hash reference of named parameters. If it receives a single argument that isn't a hash reference it throws an error.

You can override this method in your class to handle other types of options passed to the constructor.

This method should always return a hash reference of named options.

BUILD

Define a BUILD method on your class and the constructor will automatically call the BUILD method from parent down to child after the object has been instantiated. Typically this is used for object validation or possibly logging.

DEMOLISH

If you have a DEMOLISH method anywhere in your inheritance hierarchy, a DESTROY method is created on first object construction which will call $instance->DEMOLISH($in_global_destruction) for each DEMOLISH method from child upwards to parents.

Note that the DESTROY method is created on first construction of an object of your class in order to not add overhead to classes without DEMOLISH methods; this may prove slightly surprising if you try and define your own.

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 if the attribute is lazy, when the attribute is first retrieved if no value has yet been provided.

Note that if your default is fired during new() there is no guarantee that other attributes have been populated yet so you should not rely on their existence.

Takes a method name which will return true if an attribute has a value.

A common example of this would be to call it has_$foo, implying that the object has a $foo set.

builder

Takes a method name which will be called to create the attribute - functions exactly like default except that instead of calling

$default->($self);

Moo will call

$self->$builder;

clearer

Takes a method name which will clear the attribute.

lazy

Boolean. Set this if you want values for the attribute to be grabbed lazily. This is usually a good idea if you have a "builder" which requires another attribute to be set.

required

Boolean. Set this if the attribute must be passed on instantiation.

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 get_foo

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 set_foo

weak_ref

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.

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 initialization name. undef means that passing the value in on instantiation

after

SUB QUOTE AWARE

"quote_sub" in Sub::Quote allows us to create coderefs that are "inlineable," giving us a handy, XS-free speed boost. Any option that is Sub::Quote aware can take advantage of this.

INCOMPATIBILITIES WITH MOOSE

You can only compose one role at a time. If your application is large or complex enough to warrant complex composition, you wanted Moose. Note that this does not mean you can only compose one role per class -

with 'FirstRole';
with 'SecondRole';

is absolutely fine, there's just currently no equivalent of Moose's

with 'FirstRole', 'SecondRole';

which composes the two roles together, and then applies them.

There is no built in type system. 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. MooX::Types::MooseLike provides a similar API to MooseX::Types::Moose so that you can write

has days_to_live => (is => 'ro', isa => Int);

and have it work with both; it is hoped that providing only subrefs as an API will encourage the use of other type systems as well, since it's probably the weakest part of Moose design-wise.

initializer is not supported in core since the author considers it to be a bad idea but may be supported by an extension in future. Meanwhile trigger or coerce are more likely to be able to fulfill your needs.

There is no meta object. If you need this level of complexity you wanted Moose - Moo succeeds at being small because it explicitly does not provide a metaprotocol.

No support for super, override, inner, or augment - override can be handled by around albeit with a little more typing, and the author considers augment to be a bad idea.

The dump method is not provided by default. The author suggests loading Devel::Dwarn into main:: (via perl -MDevel::Dwarn ... for example) and using $obj->$::Dwarn() instead.

"default" only supports coderefs, because doing otherwise is usually a mistake anyway.

lazy_build is not supported per se, but of course it will work if you manually set all the options it implies.

auto_deref is not supported since the author considers it a bad idea.

documentation is not supported since it's a very poor replacement for POD.

Handling of warnings: when you use Moo we enable FATAL warnings. The nearest similar invocation for Moose would be:

use Moose;
use warnings FATAL => "all";

Additionally, Moo supports a set of attribute option shortcuts intended to reduce common boilerplate. The set of shortcuts is the same as in the Moose module MooseX::AttributeShortcuts as of its version 0.009+. So if you: