X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=gitmo%2FMouse.git;a=blobdiff_plain;f=lib%2FMouse.pm;h=b97cf1e1ecfaeca641881ff0d2e2ef1dab1b693b;hp=d3b1d569e61cc94220c35beeb37df101e336b331;hb=refs%2Ftags%2F0.50_04;hpb=d990f7911dfd6a36d1dcc072e7adb72bf0379349

diff --git a/lib/Mouse.pm b/lib/Mouse.pm
index d3b1d56..b97cf1e 100644
--- a/lib/Mouse.pm
+++ b/lib/Mouse.pm
@@ -3,12 +3,12 @@ use 5.006_002;
 
 use Mouse::Exporter; # enables strict and warnings
 
-our $VERSION = '0.50_02';
+our $VERSION = '0.50_04';
 
 use Carp         qw(confess);
 use Scalar::Util qw(blessed);
 
-use Mouse::Util qw(load_class is_class_loaded get_code_package not_supported);
+use Mouse::Util ();
 
 use Mouse::Meta::Module;
 use Mouse::Meta::Class;
@@ -160,7 +160,7 @@ Mouse - Moose minus the antlers
 
 =head1 VERSION
 
-This document describes Mouse version 0.50_02
+This document describes Mouse version 0.50_04
 
 =head1 SYNOPSIS
 
@@ -212,10 +212,9 @@ B<no dependencies> except for testing modules.
 
 =head2 MOOSE COMPATIBILITY
 
-Compatibility with Moose has been the utmost concern. Fewer than 1% of the
-tests fail when run against Moose instead of Mouse. Mouse code coverage is also
-over 96%. Even the error messages are taken from Moose. The Mouse code just
-runs the test suite 4x faster.
+Compatibility with Moose has been the utmost concern. The sugary interface is
+highly compatible with Moose. Even the error messages are taken from Moose.
+The Mouse code just runs the test suite 4x faster.
 
 The idea is that, if you need the extra power, you should be able to run
 C<s/Mouse/Moose/g> on your codebase and have nothing break. To that end,
@@ -226,7 +225,7 @@ Moose, if you run into weird errors, it would be worth running:
     ANY_MOOSE=Moose perl your-script.pl
 
 to see if the bug is caused by Mouse. Moose's diagnostics and validation are
-also much better.
+also better.
 
 See also L<Mouse::Spec> for compatibility and incompatibility with Moose.