Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

any::moose(3pm) [debian man page]

Any::Moose(3pm) 					User Contributed Perl Documentation					   Any::Moose(3pm)

NAME
Any::Moose - use Moose or Mouse modules VERSION
version 0.17 SYNOPSIS
BASIC package Class; # uses Moose if it's loaded or demanded, Mouse otherwise use Any::Moose; # cleans the namespace up no Any::Moose; OTHER MODULES package Other::Class; use Any::Moose; # uses Moose::Util::TypeConstraints if the class has loaded Moose, # Mouse::Util::TypeConstraints otherwise. use Any::Moose '::Util::TypeConstraints'; ROLES package My::Sorter; use Any::Moose 'Role'; requires 'cmp'; COMPLEX USAGE package My::Meta::Class; use Any::Moose; # uses subtype from Moose::Util::TypeConstraints if the class loaded Moose, # subtype from Mouse::Util::TypeConstraints otherwise. # similarly for Mo*se::Util's does_role use Any::Moose ( '::Util::TypeConstraints' => ['subtype'], '::Util' => ['does_role'], ); # uses MouseX::Types or MooseX::Types use Any::Moose 'X::Types'; # gives you the right class name depending on which Mo*se was loaded extends any_moose('::Meta::Class'); DESCRIPTION
Though we recommend that people generally use Moose, we accept that Moose cannot yet be used for everything everywhere. People generally like the Moose sugar, so many people use Mouse, a lightweight replacement for parts of Moose. Because Mouse strives for compatibility with Moose, it's easy to substitute one for the other. This module facilitates that substitution. By default, Mouse will be provided to libraries, unless Moose is already loaded -or- explicitly requested by the end-user. The end-user can force the decision of which backend to use by setting the environment variable "ANY_MOOSE" to be "Moose" or "Mouse". Note that the decision of which backend to use is made only once, so that if Any-Moose picks Mouse, then a third-party library loads Moose, anything else that uses Any-Moose will continue to pick Mouse. So, if you have to use Mouse, please be considerate to the Moose fanboys (like myself!) and use Any-Moose instead. ":)" SEE ALSO
Moose Mouse Squirrel - a deprecated first-stab at Any-Moose-like logic. Its biggest fault was in making the decision of which backend to use every time it was used, rather than just once. AUTHORS
o Shawn M Moore <sartak@bestpractical.com> o Florian Ragwitz <rafl@debian.org> o Stevan Little <stevan@iinteractive.com> o Tokuhiro Matsuno <tokuhirom@gmail.com> o Goro Fuji <gfuji@cpan.org> COPYRIGHT AND LICENSE
This software is copyright (c) 2011 by Best Practical Solutions. This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself. perl v5.12.4 2011-09-16 Any::Moose(3pm)

Check Out this Related Man Page

Mouse::Spec(3pm)					User Contributed Perl Documentation					  Mouse::Spec(3pm)

NAME
Mouse::Spec - To what extent Mouse is compatible with Moose VERSION
This document describes Mouse version 0.99 SYNOPSIS
use Mouse::Spec; printf "Mouse/%s is compatible with Moose/%s ", Mouse::Spec->MouseVersion, Mouse::Spec->MooseVersion; DESCRIPTION
Mouse is a subset of Moose. This document describes to what extend Mouse is compatible (and incompatible) with Moose. Compatibility with Moose Sugary APIs The sugary APIs are highly compatible with Moose. Methods which have the same name as Moose's are expected to be compatible with Moose's. Meta object protocols Meta object protocols are a subset of the counterpart of Moose. Their methods which have the same name as Moose's are expected to be compatible with Moose's. Feel free to use these methods even if they are not documented. However, there are differences between Moose's MOP and Mouse's. For example, meta object protocols in Mouse have no attributes by default, so "$metaclass->meta->make_immutable()" will not work as you expect. Don not make metaclasses immutable. Mouse::Meta::Instance Meta instance mechanism is not implemented, so you cannot change the reftype of Mouse objects in the same way as Moose. Role exclusion Role exclusion, "exclude()", is not implemented. -metaclass in Mouse::Exporter "use Mouse -metaclass => ..." are not implemented. Use "use Mouse -traits => ..." instead. Mouse::Meta::Attribute::Native Native traits are not supported directly, but "MouseX::NativeTraits" is available on CPAN. Once you have installed it, you can use it as the same way in Moose. That is, native traits are automatically loaded by Mouse. See MouseX::NativeTraits for details. Notes about Moose::Cookbook Many recipes in Moose::Cookbook fit Mouse, including: o Moose::Cookbook::Basics::Recipe1 - The (always classic) Point example o Moose::Cookbook::Basics::Recipe2 - A simple BankAccount example o Moose::Cookbook::Basics::Recipe3 - A lazy BinaryTree example o Moose::Cookbook::Basics::Recipe4 - Subtypes, and modeling a simple Company class hierarchy o Moose::Cookbook::Basics::Recipe5 - More subtypes, coercion in a Request class o Moose::Cookbook::Basics::Recipe6 - The augment/inner example o Moose::Cookbook::Basics::Recipe7 - Making Moose fast with immutable o Moose::Cookbook::Basics::Recipe8 - Builder methods and lazy_build o Moose::Cookbook::Basics::Recipe9 - Operator overloading, subtypes, and coercion o Moose::Cookbook::Basics::Recipe10 - Using BUILDARGS and BUILD to hook into object construction o Moose::Cookbook::Roles::Recipe1 - The Moose::Role example o Moose::Cookbook::Roles::Recipe2 - Advanced Role Composition - method exclusion and aliasing o Moose::Cookbook::Roles::Recipe3 - Applying a role to an object instance o Moose::Cookbook::Meta::Recipe2 - A meta-attribute, attributes with labels o Moose::Cookbook::Meta::Recipe3 - Labels implemented via attribute traits o Moose::Cookbook::Extending::Recipe3 - Providing an alternate base object class SEE ALSO
Mouse Moose Moose::Manual Moose::Cookbook perl v5.14.2 2012-06-30 Mouse::Spec(3pm)
Man Page