X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FMoose%2FMeta%2FTypeCoercion.pm;h=8f59343e1a8bc10bb1e8ab9a89d8904b0567bb7a;hb=baf46b9edc7dc3665c7eaf9d1684b157efb09e1a;hp=6ce45c1ab04e39fe0f677c077eabf9d114d0c75c;hpb=b2ad68e3fbe4016e354980a636c1ed39e941162a;p=gitmo%2FMoose.git diff --git a/lib/Moose/Meta/TypeCoercion.pm b/lib/Moose/Meta/TypeCoercion.pm index 6ce45c1..8f59343 100644 --- a/lib/Moose/Meta/TypeCoercion.pm +++ b/lib/Moose/Meta/TypeCoercion.pm @@ -8,7 +8,7 @@ use metaclass; use Moose::Meta::Attribute; use Moose::Util::TypeConstraints (); -our $VERSION = '0.67'; +our $VERSION = '0.72_01'; $VERSION = eval $VERSION; our $AUTHORITY = 'cpan:STEVAN'; @@ -43,8 +43,12 @@ sub compile_type_coercion { while (@coercion_map) { my ($constraint_name, $action) = splice(@coercion_map, 0, 2); my $type_constraint = ref $constraint_name ? $constraint_name : Moose::Util::TypeConstraints::find_or_parse_type_constraint($constraint_name); - (defined $type_constraint) - || Moose->throw_error("Could not find the type constraint ($constraint_name) to coerce from"); + + unless ( defined $type_constraint ) { + require Moose; + Moose->throw_error("Could not find the type constraint ($constraint_name) to coerce from"); + } + push @coercions => [ $type_constraint->_compiled_type_constraint, $action @@ -77,10 +81,12 @@ sub add_type_coercions { while (@new_coercion_map) { my ($constraint_name, $action) = splice(@new_coercion_map, 0, 2); - - Moose->throw_error("A coercion action already exists for '$constraint_name'") - if exists $has_coercion{$constraint_name}; - + + if ( exists $has_coercion{$constraint_name} ) { + require Moose; + Moose->throw_error("A coercion action already exists for '$constraint_name'") + } + push @{$coercion_map} => ($constraint_name, $action); } @@ -103,34 +109,66 @@ Moose::Meta::TypeCoercion - The Moose Type Coercion metaclass =head1 DESCRIPTION -For the most part, the only time you will ever encounter an -instance of this class is if you are doing some serious deep -introspection. This API should not be considered final, but -it is B that this will matter to a regular -Moose user. +A type coercion object is basically a mapping of one or more type +constraints and the associated coercions subroutines. -If you wish to use features at this depth, please come to the -#moose IRC channel on irc.perl.org and we can talk :) +It's unlikely that you will need to instantiate an object of this +class directly, as it's part of the deep internals of Moose. =head1 METHODS =over 4 -=item B +=item B<< Moose::Meta::TypeCoercion->new(%options) >> + +Creates a new type coercion object, based on the options provided. + +=over 8 + +=item * type_constraint + +This is the L object for the type that is +being coerced I. + +=back + +=item B<< $coercion->type_coercion_map >> + +This returns the map of type constraints to coercions as an array +reference. The values of the array alternate between type names and +subroutine references which implement the coercion. + +The value is an array reference because coercions are tried in the +order they are added. + +=item B<< $coercion->type_constraint >> + +This returns the L that was passed to the +constructor. + +=item B<< $coercion->has_coercion_for_type($type_name) >> + +Returns true if the coercion can coerce the named type. + +=item B<< $coercion->add_type_coercions( $type_name => $sub, ... ) >> -=item B +This method takes a list of type names and subroutine references. If +the coercion already has a mapping for a given type, it throws an +exception. -=item B +Coercions are actually -=item B +=item B<< $coercion->coerce($value) >> -=item B +This method takes a value and applies the first valid coercion it +finds. -=item B +This means that if the value could belong to more than type in the +coercion object, the first coercion added is used. -=item B +=item B<< Moose::Meta::TypeCoercion->meta >> -=item B +This will return a L instance for this class. =back