NAME

Moose::Cookbook - How to cook a Moose

DESCRIPTION

The Moose cookbook is a series of recipes taken from the Moose test suite. Each recipe presents some code, which demonstrates some of the features of Moose, and then proceeds to explain the details of the code.

We also provide a Moose::Cookbook::FAQ and a Moose::Cookbook::WTF for common questions and problems people have with Moose.

RECIPES

Basic Moose

These recipes will give you a good idea of what Moose is capable, starting with simple attribute declaration, and moving on to more powerful features like laziness, types, type coercion, method modifiers, and more.

Moose::Cookbook::Basics::Recipe1 - The (always classic) Point example

A simple Moose-based class. Demonstrated Moose attributes and subclassing.

Moose::Cookbook::Basics::Recipe2 - A simple BankAccount example

A slightly more complex Moose class. Demonstrates using a method modifier in a subclass.

Moose::Cookbook::Basics::Recipe3 - A lazy BinaryTree example

Demonstrates several attribute features, including types, weak references, predicates ("does this object have a foo?"), defaults, and lazy attribute uction.

Moose::Cookbook::Basics::Recipe4 - Subtypes, and modeling a simple Company class hierarchy

Introduces the creation and use of custom types, a BUILD method, and the use of override in a subclass.

Moose::Cookbook::Basics::Recipe5 - More subtypes, coercion in a Request class

More type examples, including the use of type coercions.

Moose::Cookbook::Basics::Recipe6 - The augment/inner example

Demonstrates the use of augment method modifiers, a way of turning the usual method overriding style "inside-out".

Moose::Cookbook::Basics::Recipe7 - Making Moose fast with immutable

Making a class immutable greatly increases the speed of accessors and object construction.

Moose::Cookbook::Basics::Recipe8 - Managing complex relations with trigger (TODO)

abstract goes here

Work off of this http://code2.0beta.co.uk/moose/svn/Moose/trunk/t/200_examples/007_Child_Parent_attr_inherit.t

Moose::Cookbook::Basics::Recipe9 - Builder methods and lazy_build

The builder feature provides an inheritable and role-composable way to provide a default attribute value.

Moose::Cookbook::Basics::Recipe10 - Operator overloading, subtypes, and coercion

Demonstrates using operator overloading, coercion, and subtypes to model how eye color is determined during reproduction.

Moose Roles

These recipes will show you how to use Moose roles.

Moose::Cookbook::Role::Recipe1 - The Moose::Role example

Demonstrates roles, which are also sometimes known as traits or mix-ins. Roles provide a method of code re-use which is orthogonal to subclassing.

Moose::Cookbook::Role::Recipe2 - Advanced Role Composition - method exclusion and aliasing

Sometimes you just want to include part of a role in your class. Sometimes you want the whole role but one if its methods conflicts with one in your class. With method exclusion and aliasing, you can work around these problems.

Moose::Cookbook::Role::Recipe3 - Runtime Role Composition (TODO)

abstract goes here

Meta Moose

These recipes show you how to write your own meta classes, which lets you extend the object system provide by Moose.

Moose::Cookbook::Meta::Recipe1 - Welcome to the meta-world (Why Go Meta?)

If you're wondering what all this "meta" stuff is, and why you should care about it, read this "recipe".

Moose::Cookbook::Meta::Recipe2 - A meta-attribute, attributes with labels

One way to extend Moose is to provide your own attribute metaclasses. Attribute metaclasses let you extend attribute declarations (with has) and behavior to provide additional attribute functionality.

Moose::Cookbook::Meta::Recipe3 - Labels implemented via attribute traits

Extending Moose's attribute metaclass is a great way to add functionality. However, attributes can only have one metaclass. Applying roles to the attribute metaclass lets you provide composable attribute functionality.

Moose::Cookbook::Meta::Recipe4 - Adding a "table" attribute to the metaclass

If you want to store more information about your classes, you'll have to extend Moose::Meta::Class. Doing so is simple, but you'll probably also want to provide some sugar, so see Moose::Cookbook::Meta::Recipe6 as well.

Moose::Cookbook::Meta::Recipe5 - The "table" attribute implemented via a metaclass trait

abstract goes here

Moose::Cookbook::Meta::Recipe6 - Hooking into the immutabilization system (TODO)

Moose has a feature known as "immutabilization". By calling __PACKAGE__->meta()->make_immutable() after defining your class (attributes, roles, etc), you tell Moose to optimize things like object creation, attribute access, and so on.

If you are creating your own metaclasses, you may need to hook into the immutabilization system. This cuts across a number of spots, including the metaclass class, meta method classes, and possibly the meta-instance class as well.

This recipe shows you how to write extensions which immutabilize properly.

Moose::Cookbook::Meta::Recipe7 - meta-instance (TODO)

abstract goes here

Extending Moose

These recipes cover some more ways to extend Moose, and will be useful if you plan to write your own MooseX module.

Moose::Cookbook::Extending::Recipe1 - Providing an alternate base object class

You may find that you want to provide an alternate base object class along with a meta extension, or maybe you just want to add some functionality to all your classes without typing extends 'MyApp::Base' over and over.

Moose::Cookbook::Extending::Recipe2 - Acting like Moose.pm and providing sugar Moose-style

This recipe shows how to provide a replacement for Moose.pm. This is something that you may want to do as part of a MooseX module, especially if you want to default to a new metaclass class or base object class.

SNACKS

Moose::Cookbook::Snack::Keywords

Moose::Cookbook::Snack::Types

SEE ALSO

http://www.gsph.com/index.php?Lang=En&ID=291

AUTHOR

Stevan Little <stevan@iinteractive.com>

COPYRIGHT AND LICENSE

Copyright 2006-2008 by Infinity Interactive, Inc.

http://www.iinteractive.com

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.