use Moo::_Utils;
use B 'perlstring';
-our $VERSION = '0.009013'; # 0.9.13
+our $VERSION = '0.009014'; # 0.9.13
$VERSION = eval $VERSION;
+sub Moo::HandleMoose::AuthorityHack::DESTROY {
+ require Moo::HandleMoose;
+ Moo::HandleMoose->import;
+}
+
+if ($INC{"Moose.pm"}) {
+ require Moo::HandleMoose;
+ Moo::HandleMoose->import;
+} else {
+ $Moose::AUTHORITY = bless({}, 'Moo::HandleMoose::AuthorityHack');
+}
+
our %MAKERS;
sub import {
};
*{_getglob("${target}::with")} = sub {
require Moo::Role;
- die "Only one role supported at a time by with" if @_ > 1;
- Moo::Role->apply_role_to_package($target, $_[0]);
+ Moo::Role->apply_roles_to_package($target, $_[0]);
};
$MAKERS{$target} = {};
*{_getglob("${target}::has")} = sub {
require Moo::Object; ('Moo::Object');
} unless @{"${target}::ISA"};
}
+ if ($INC{'Moo/HandleMoose.pm'}) {
+ Moo::HandleMoose::inject_fake_metaclass_for($target);
+ }
}
sub _constructor_maker_for {
=head1 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 L<Moose>.
+complex enough to warrant complex composition, you wanted L<Moose>. Note that
+this does not mean you can only compose one role per class -
+
+ with 'FirstRole';
+ with 'SecondRole';
-There is no complex type system. C<isa> is verified with a coderef, if you
+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. C<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.
+that return quoted subs. L<MooX::Types::MooseLike> provides a similar API
+to L<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.
C<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.
be handled by around albeit with a little more typing, and the author considers
augment to be a bad idea.
+The C<dump> method is not provided by default. The author suggests loading
+L<Devel::Dwarn> into C<main::> (via C<perl -MDevel::Dwarn ...> for example) and
+using C<$obj-E<gt>$::Dwarn()> instead.
+
L</default> only supports coderefs, because doing otherwise is usually a
mistake anyway.
use warnings FATAL => "all";
use MooseX::AttributeShortcuts;
+or, if you're inheriting from a non-Moose class,
+
+ package MyClass;
+
+ use Moose;
+ use MooseX::NonMoose;
+ use warnings FATAL => "all";
+ use MooseX::AttributeShortcuts;
+
+Finally, Moose requires you to call
+
+ __PACKAGE__->meta->make_immutable;
+
+at the end of your class to get an inlined (i.e. not horribly slow)
+constructor. Moo does it automatically the first time ->new is called
+on your class.
+
=head1 AUTHOR
mst - Matt S. Trout (cpan:MSTROUT) <mst@shadowcat.co.uk>
doy - Jesse Luehrs (cpan:DOY) <doy at tozt dot net>
+perigrin - Chris Prather (cpan:PERIGRIN) <chris@prather.org>
+
=head1 COPYRIGHT
Copyright (c) 2010-2011 the Moo L</AUTHOR> and L</CONTRIBUTORS>