use B 'perlstring';
use Sub::Defer ();
-our $VERSION = '0.091003'; # 0.91.3
+our $VERSION = '0.091007'; # 0.91.7
$VERSION = eval $VERSION;
require Moo::sification;
Moo->_constructor_maker_for($target)
->register_attribute_specs(%{$old->all_attribute_specs});
}
+ $Moo::HandleMoose::MOUSE{$target} = [
+ grep defined, map Mouse::Util::find_meta($_), @_
+ ] if $INC{"Mouse.pm"};
+ $class->_maybe_reset_handlemoose($target);
+ return;
};
_install_coderef "${target}::with" => "Moo::with" => sub {
require Moo::Role;
Moo::Role->apply_roles_to_package($target, $_[0]);
+ $class->_maybe_reset_handlemoose($target);
};
$MAKERS{$target} = {};
_install_coderef "${target}::has" => "Moo::has" => sub {
->register_attribute_specs($name, \%spec);
$class->_accessor_maker_for($target)
->generate_method($target, $name, \%spec);
+ $class->_maybe_reset_handlemoose($target);
+ return;
};
foreach my $type (qw(before after around)) {
_install_coderef "${target}::${type}" => "Moo::${type}" => sub {
require Class::Method::Modifiers;
_install_modifier($target, $type, @_);
+ return;
};
}
{
}
}
+sub _maybe_reset_handlemoose {
+ my ($class, $target) = @_;
+ if ($INC{"Moo/HandleMoose.pm"}) {
+ Moo::HandleMoose::maybe_reinject_fake_metaclass_for($target);
+ }
+}
+
sub _accessor_maker_for {
my ($class, $target) = @_;
return unless $MAKERS{$target};
Extending a L<Moose> class or consuming a L<Moose::Role> should also work.
+So should extending a L<Mouse> class or consuming a L<Mouse::Role>.
+
This means that there is no need for anything like L<Any::Moose> for Moo
-code - Moo and Moose code should simply interoperate without problem.
+code - Moo and Moose code should simply interoperate without problem. To
+handle L<Mouse> code, you'll likely need an empty Moo role or class consuming
+or extending the L<Mouse> stuff since it doesn't register true L<Moose>
+metaclasses like we do.
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.
=item * is
-B<required>, may be C<ro>, C<rw>, C<lazy> or C<rwp>.
+B<required>, may be C<ro>, C<lazy>, C<rwp> or C<rw>.
C<ro> generates an accessor that dies if you attempt to write to it - i.e.
a getter only - by defaulting C<reader> to the name of the attribute.
-C<rw> generates a normal getter/setter by defauting C<accessor> to the
-name of the attribute.
-
C<lazy> generates a reader like C<ro>, but also sets C<lazy> to 1 and
C<builder> to C<_build_${attribute_name}> to allow on-demand generated
attributes. This feature was my attempt to fix my incompetence when
from inside of the class, but read-only from outside.
This feature comes from L<MooseX::AttributeShortcuts>.
+C<rw> generates a normal getter/setter by defaulting C<accessor> to the
+name of the attribute.
+
=item * isa
Takes a coderef which is meant to validate the attribute. Unlike L<Moose> Moo
L<Sub::Quote aware|/SUB QUOTE AWARE>
+Since L<Moo> does B<not> run the C<isa> check before C<coerce> if a coercion
+subroutine has been supplied, C<isa> checks are not structural to your code
+and can, if desired, be omitted on non-debug builds (although if this results
+in an uncaught bug causing your program to break, the L<Moo> authors guarantee
+nothing except that you get to keep both halves).
+
If you want L<MooseX::Types> style named types, look at
L<MooX::Types::MooseLike>.
$_[0] + 1 unless $_[0] % 2
},
-Coerce does not require C<isa> to be defined, but since L<Moose> does
-require it, the metaclass inflation for coerce-alone is a trifle insane
-and if you attempt to subtype the result will almost certainly break.
+Note that L<Moo> will always fire your coercion - this is to permit
+isa entries to be used purely for bug trapping, whereas coercions are
+always structural to your code. We do, however, apply any supplied C<isa>
+check after the coercion has run to ensure that it returned a valid value.
L<Sub::Quote aware|/SUB QUOTE AWARE>
will return an appropriate metaclass pre-populated by L<Moo>.
-No support for C<super>, C<override>, C<inner>, or C<augment> - override can
-be handled by around albeit with a little more typing, and the author considers
-augment to be a bad idea.
+No support for C<super>, C<override>, C<inner>, or C<augment> - the author
+considers augment to be a bad idea, and override can be translated:
+
+ override foo => sub {
+ ...
+ super();
+ ...
+ };
+
+ around foo => sub {
+ my ($orig, $self) = (shift, shift);
+ ...
+ $self->$orig(@_);
+ ...
+ };
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
C<auto_deref> is not supported since the author considers it a bad idea.
C<documentation> will show up in a L<Moose> metaclass created from your class
-but is otherwise ignored. Then again, L<Moose> ignors it as well, so this
+but is otherwise ignored. Then again, L<Moose> ignores it as well, so this
is arguably not an incompatibility.
+Since C<coerce> does not require C<isa> to be defined but L<Moose> does
+require it, the metaclass inflation for coerce-alone is a trifle insane
+and if you attempt to subtype the result will almost certainly break.
+
Handling of warnings: when you C<use Moo> we enable FATAL warnings. The nearest
similar invocation for L<Moose> would be: