use Scalar::Util 'blessed';
use Moose::Util::TypeConstraints ();
-our $VERSION = '0.56';
+our $VERSION = '0.72';
+$VERSION = eval $VERSION;
our $AUTHORITY = 'cpan:STEVAN';
use base 'Moose::Meta::TypeConstraint';
my ( $class, %args ) = @_;
$args{parent} = Moose::Util::TypeConstraints::find_type_constraint('Object');
- my $self = $class->meta->new_object(%args);
+ my $self = $class->_new(\%args);
$self->_create_hand_optimized_type_constraint;
$self->compile_type_constraint();
my $other = Moose::Util::TypeConstraints::find_type_constraint($type_or_name);
+ return unless defined $other;
return unless $other->isa(__PACKAGE__);
return $self->class eq $other->class;
}
my $type = Moose::Util::TypeConstraints::find_type_constraint($type_or_name_or_class);
+
+ return unless defined $type;
if ( $type->isa(__PACKAGE__) ) {
# if $type_or_name_or_class isn't a class, it might be the TC name of another ::Class type
}
}
+# This is a bit counter-intuitive, but a child type of a Class type
+# constraint is not itself a Class type constraint (it has no class
+# attribute). This whole create_child_type thing needs some changing
+# though, probably making MMC->new a factory or something.
+sub create_child_type {
+ my ($self, @args) = @_;
+ return Moose::Meta::TypeConstraint->new(@args, parent => $self);
+}
+
1;
__END__
Moose::Meta::TypeConstraint::Class - Class/TypeConstraint parallel hierarchy
+=head1 DESCRIPTION
+
+This class represents type constraints for a class.
+
+=head1 INHERITANCE
+
+C<Moose::Meta::TypeConstraint::Class> is a subclass of
+L<Moose::Meta::TypeConstraint>.
+
=head1 METHODS
=over 4
-=item B<new>
+=item B<< Moose::Meta::TypeConstraint::Class->new(%options) >>
+
+This creates a new class type constraint based on the given
+C<%options>.
+
+It takes the same options as its parent, with two exceptions. First,
+it requires an additional option, C<class>, which is name of the
+constraint's class. Second, it automatically sets the parent to the
+C<Object> type.
+
+The constructor also overrides the hand optimized type constraint with
+one it creates internally.
+
+=item B<< $constraint->class >>
-=item B<class>
+Returns the class name associated with the constraint.
-=item B<hand_optimized_type_constraint>
+=item B<< $constraint->parents >>
-=item B<has_hand_optimized_type_constraint>
+Returns all the type's parent types, corresponding to its parent
+classes.
-=item B<equals>
+=item B<< $constraint->is_a_subtype_of($type_name_or_object) >>
-=item B<is_a_type_of>
+If the given type is also a class type, then this checks that the
+type's class is a subclass of the other type's class.
-=item B<is_subtype_of>
+Otherwise it falls back to the implementation in
+L<Moose::Meta::TypeConstraint>.
-=item B<parents>
+=item B<< $constraint->create_child_type(%options) >>
-Return all the parent types, corresponding to the parent classes.
+This returns a new L<Moose::Meta::TypeConstraint> object with the type
+as its parent.
-=item B<meta>
+Note that it does I<not> return a
+C<Moose::Meta::TypeConstraint::Class> object!
=back
=head1 COPYRIGHT AND LICENSE
-Copyright 2006-2008 by Infinity Interactive, Inc.
+Copyright 2006-2009 by Infinity Interactive, Inc.
L<http://www.iinteractive.com>