From: John Napiorkowski Date: Mon, 28 Jun 2010 17:24:23 +0000 (-0400) Subject: updated readme and doc tweak X-Git-Tag: 0.05~4 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=461e0f82c65c1c217c305e0f5d9be097630dc8fe;p=gitmo%2FMooseX-Dependent.git updated readme and doc tweak --- diff --git a/README b/README index ad26d6c..fffa7e6 100644 --- a/README +++ b/README @@ -61,7 +61,8 @@ DESCRIPTION parameterizable type constraint for all intents and uses is a subclass of a parent type, but adds additional type parameters which are available to constraint callbacks (such as inside the 'where' clause of - a type constraint definition) or in the coercions. + a type constraint definition) or in the coercions you define for a given + type constraint. If you have Moose experience, you probably are familiar with the builtin parameterizable type constraints 'ArrayRef' and 'HashRef'. This type @@ -91,16 +92,28 @@ DESCRIPTION RangedInt([{min=>10,max=>100}])->check(50); ## OK RangedInt([{min=>50, max=>75}])->check(99); ## Not OK, exceeds max - The type parameter must be valid against the type constraint given. If - you pass an invalid value this throws a hard Moose exception. You'll - need to capture it in an eval or related exception catching system (see - TryCatch or .) For example the following would throw a hard - error (and not just return false) + This is useful since it lets you generate common patterns of type + constraints rather than build a custom type constraint for all similar + cases. + + The type parameter must be valid against the 'constrainting' type + constraint used in the Parameterizable condition. If you pass an invalid + value this throws a hard Moose exception. You'll need to capture it in + an eval or related exception catching system (see TryCatch or + Try::Tiny.) + + For example the following would throw a hard error (and not just return + false) RangedInt([{min=>99, max=>10}])->check(10); ## Not OK, not a valid Range! - If you can't accept a hard exception here, you'll need to test the - constraining values first, as in: + In the above case the 'min' value is larger than the 'max', which + violates the Range constraint. We throw a hard error here since I think + incorrect type parameters are most likely to be the result of a typo or + other true error conditions. + + If you can't accept a hard exception here, you can either trap it as + advised above or you need to test the constraining values first, as in: my $range = {min=>99, max=>10}; if(my $err = Range->validate($range)) { @@ -119,8 +132,7 @@ DESCRIPTION RangedInt([min=>99, max=>10])->check(10); ## Exception, not valid Range This is the preferred syntax, as it improve readability and adds to the - conciseness of your type constraint declarations. An exception wil be - thrown if your type parameters don't match the required reference type. + conciseness of your type constraint declarations. Also note that if you 'chain' parameterization results with a method call like: @@ -154,8 +166,8 @@ DESCRIPTION shift >= 0; }; - In this case you'd now have a parameterizable type constraint called - which would work like: + In this case you'd now have a parameterizable type constraint which + would work like: Test::More::ok PositiveRangedInt([{min=>-10, max=>75}])->check(5); Test::More::ok !PositiveRangedInt([{min=>-10, max=>75}])->check(-5); @@ -200,14 +212,15 @@ DESCRIPTION In other words, given the example above, a type constraint of 'RangedInt' would have a parent of 'Int', not 'Parameterizable' and for - all intends and uses you could stick it wherever you'd need an Int. + all intends and uses you could stick it wherever you'd need an Int. You + can't change the parent, even to make it a subclass of Int. Coercions - A type coerction is a rule that allows you to transform one type from - one or more other types. Please see Moose::Cookbook::Basics::Recipe5 for - an example of type coercions if you are not familiar with the subject. + A type coercion is a rule that allows you to transform one type from one + or more other types. Please see Moose::Cookbook::Basics::Recipe5 for an + example of type coercions if you are not familiar with the subject. - MooseX::Types::Parameterizable support type coercions in all the ways + MooseX::Types::Parameterizable supports type coercions in all the ways you would expect. In addition, it also supports a limited form of type coercion inheritance. Generally speaking, type constraints don't inherit coercions since this would rapidly become confusing. However, since your @@ -217,7 +230,7 @@ DESCRIPTION For the purposes of this discussion, a parameterizable type is a subtype created when you say, "as Parameterizable[..." in your sub type - declaration. For example + declaration. For example: subtype Varchar, as Parameterizable[Str, Int], @@ -227,7 +240,7 @@ DESCRIPTION }, message { "'$_' is too long" }; - This is the example, which creates a new parameterizable + This is the "SYNOPSIS" example, which creates a new parameterizable subtype of Str which takes a single type parameter which must be an Int. This Int is used to constrain the allowed length of the Str value. @@ -244,7 +257,7 @@ DESCRIPTION use directly to constraint a value. In other words you'd never do something like: - has name => (isa=>Varchar, ...) + has name => (isa=>Varchar, ...); ## Why not just use a Str? You are going to do this: @@ -290,15 +303,18 @@ DESCRIPTION TYPE CONSTRAINTS This type library defines the following constraints. - Parameterizable[ParentTypeConstraint, ParameterizableValueTypeConstraint] + Parameterizable[ParentTypeConstraint, ConstrainingValueTypeConstraint] Create a subtype of ParentTypeConstraint with a dependency on a value - that can pass the ParameterizableValueTypeConstraint. If - ParameterizableValueTypeConstraint is empty we default to the 'Any' type - constraint (see Moose::Util::TypeConstraints). + that can pass the ConstrainingValueTypeConstraint. If + ConstrainingValueTypeConstraint is empty we default to the 'Any' type + constraint (see Moose::Util::TypeConstraints). This is useful if you are + creating some base Parameterizable type constraints that you intend to + sub class. + +SEE ALSO + The following modules or resources may be of interest. - This creates a type constraint which must be further parameterized at - later time before it can be used to ->check or ->validate a value. - Attempting to do so will cause an exception. + Moose, Moose::Meta::TypeConstraint, MooseX::Types AUTHOR John Napiorkowski, "" diff --git a/lib/MooseX/Types/Parameterizable.pm b/lib/MooseX/Types/Parameterizable.pm index 48ac2db..58bb350 100644 --- a/lib/MooseX/Types/Parameterizable.pm +++ b/lib/MooseX/Types/Parameterizable.pm @@ -223,7 +223,7 @@ to make it a subclass of Int. =head2 Coercions -A type coerction is a rule that allows you to transform one type from one or +A type coercion is a rule that allows you to transform one type from one or more other types. Please see L for an example of type coercions if you are not familiar with the subject.