switching over to dzil

[gitmo/MooseX-Types.git] / lib / MooseX / Types.pm

diff --git a/lib/MooseX/Types.pm b/lib/MooseX/Types.pm
index 33f26d7..4f16f9a 100644 (file)
--- a/lib/MooseX/Types.pm
+++ b/lib/MooseX/Types.pm
@@ -1,11 +1,7 @@
 package MooseX::Types;
 use Moose;
 
-=head1 NAME
-
-MooseX::Types - Organise your Moose types in libraries
-
-=cut
+# ABSTRACT: Organise your Moose types in libraries
 
 use Moose::Util::TypeConstraints;
 use MooseX::Types::TypeDecorator;
@@ -20,7 +16,6 @@ use Scalar::Util                      'reftype';
 use namespace::clean -except => [qw( meta )];
 
 use 5.008;
-our $VERSION = '0.19';
 my $UndefMsg = q{Action for type '%s' not yet defined in library '%s'};
 
 =head1 SYNOPSIS
@@ -152,7 +147,7 @@ return a false value if the type could not be coerced.
 
 B<Important Note>: This handler will only be exported for types that can
 do type coercion. This has the advantage that a coercion to a type that
-cannot hasn't defined any coercions will lead to a compile-time error.
+has not defined any coercions will lead to a compile-time error.
 
 =head1 LIBRARY DEFINITION
 
@@ -213,7 +208,7 @@ of a set of library exports. Here is an example:
 
   package MyWrapper;
   use strict;
-  use Class::C3;
+  use MRO::Compat;
   use base 'MooseX::Types::Wrapper';
 
   sub coercion_export_generator {
@@ -527,7 +522,7 @@ Due to this stringification, the following will NOT work as you might think:
 
   subtype StrOrArrayRef => as Str|ArrayRef;
   
-The 'StrOrArrayRef' will have it's stringification activated this causes the
+The 'StrOrArrayRef' will have its stringification activated this causes the
 subtype to not be created.  Since the bareword type constraints are not strings
 you really should not try to treat them that way.  You will have to use the ','
 operator instead.  The author's of this package realize that all the L<Moose>
@@ -571,7 +566,15 @@ This is a workaround and I am exploring how to make these modules work better
 together.  I realize this workaround will lead a lot of duplication in your
 export declarations and will be onerous for large type libraries.  Patches and
 detailed test cases welcome. See the tests directory for a start on this.
-    
+
+=head1 COMBINING TYPE LIBRARIES
+
+You may want to combine a set of types for your application with other type
+libraries, like L<MooseX::Types::Moose> or L<MooseX::Types::Common::String>.
+
+The L<MooseX::Types::Combine> module provides a simple API for combining a set
+of type libraries together.
+
 =head1 SEE ALSO
 
 L<Moose>, 
@@ -583,10 +586,6 @@ L<Sub::Exporter>
 
 Many thanks to the C<#moose> cabal on C<irc.perl.org>.
 
-=head1 AUTHOR
-
-Robert "phaylon" Sedlacek <rs@474.at>
-
 =head1 CONTRIBUTORS
 
 jnapiorkowski: John Napiorkowski <jjnapiork@cpan.org>
@@ -597,12 +596,7 @@ rafl: Florian Ragwitz <rafl@debian.org>
 
 hdp: Hans Dieter Pearcey <hdp@cpan.org>
 
-=head1 COPYRIGHT & LICENSE
-
-Copyright (c) 2007-2009 Robert Sedlacek <rs@474.at>
-
-This program is free software; you can redistribute it and/or modify
-it under the same terms as perl itself.
+autarch: Dave Rolsky <autarch@urth.org>
 
 =cut