NAME
Any::Moose - *deprecated* - use Moo instead!
VERSION
version 0.19
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. :)
DEPRECATION
Please use Moo instead of Any::Moose for new code.
Moo classes and roles will transparently and correctly upgrade to Moose when needed. This is a fundamentally better design than what Any::Moose offers. Mouse metaclasses do not interact with Moose metaclasses which leaks abstractions all over the place.
Any::Moose had a good run. It was a simplistic but expedient answer for getting Moose syntax on the cheap but with the transparent upgrade path to Moose when you needed it. But really, please don't use it any more. :)
You may find MooX::late useful for porting your code from Any::Moose to Moo.
SEE ALSO
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
Shawn M Moore <sartak@gmail.com>
Florian Ragwitz <rafl@debian.org>
Stevan Little <stevan@iinteractive.com>
Tokuhiro Matsuno <tokuhirom@gmail.com>
Goro Fuji <gfuji@cpan.org>
Ricardo Signes <rjbs@cpan.org>
COPYRIGHT AND LICENSE
This software is copyright (c) 2012 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.