return if $MAKERS{$target}; # already exported into this package
*{_getglob("${target}::extends")} = sub {
_load_module($_) for @_;
- *{_getglob("${target}::ISA")} = \@_;
+ # Can't do *{...} = \@_ or 5.10.0's mro.pm stops seeing @ISA
+ @{*{_getglob("${target}::ISA")}{ARRAY}} = @_;
};
*{_getglob("${target}::with")} = sub {
require Moo::Role;
1;
-=pod
-
=head1 NAME
Moo - Minimalist Object Orientation (with Moose compatiblity)
+=head1 WARNING WARNING WARNING
+
+This is a 0.9 release because we're fairly sure it works. For us. Until it's
+tested in the wild, we make no guarantees it also works for you.
+
+If this module does something unexpected, please submit a failing test.
+
+But if it eats your cat, sleeps with your boyfriend, or pushes grandma down
+the stairs to save her from the terrible secret of space, it's not our fault.
+
=head1 SYNOPSIS
package Cat::Food;
Unlike C<Mouse> this module does not aim at full L<Moose> compatibility. See
L</INCOMPATIBILITIES> for more details.
+=head1 WHY MOO EXISTS
+
+If you want a full object system with a rich Metaprotocol, L<Moose> is
+already wonderful.
+
+I've tried several times to use L<Mouse> but it's 3x the size of Moo and
+takes longer to load than most of my Moo based CGI scripts take to run.
+
+If you don't want L<Moose>, you don't want "less metaprotocol" like L<Mouse>,
+you want "as little as possible" - which means "no metaprotocol", which is
+what Moo provides.
+
+By Moo 1.0 I intend to have Moo's equivalent of L<Any::Moose> built in -
+if Moose gets loaded, any Moo class or role will act as a Moose equivalent
+if treated as such.
+
+Hence - Moo exists as its name - Minimal Object Orientation - with a pledge
+to make it smooth to upgrade to L<Moose> when you need more than minimal
+features.
+
=head1 IMPORTED METHODS
=head2 new