From: Chris Prather <chris@prather.org>
Date: Thu, 25 Jun 2009 15:47:23 +0000 (-0400)
Subject: add docs for ducktype handles that Sartak wrote
X-Git-Tag: 0.84~26
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=e3de240e655f086aa3d781e13385eeca44da9e85;p=gitmo%2FMoose.git

add docs for ducktype handles that Sartak wrote
---

diff --git a/lib/Moose.pm b/lib/Moose.pm
index ea6b6c2..8f11db5 100644
--- a/lib/Moose.pm
+++ b/lib/Moose.pm
@@ -469,7 +469,7 @@ B<NOTE:> Triggers will only fire when you B<assign> to the attribute,
 either in the constructor, or using the writer. Default and built values will
 B<not> cause the trigger to be fired.
 
-=item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | CODE>
+=item I<handles =E<gt> ARRAY | HASH | REGEXP | ROLE | DUCKTYPE | CODE>
 
 The I<handles> option provides Moose classes with automated delegation features.
 This is a pretty complex and powerful option. It accepts many different option
@@ -561,6 +561,14 @@ methods of the role and any required methods of the role. It should be noted
 that this does B<not> include any method modifiers or generated attribute
 methods (which is consistent with role composition).
 
+=item C<DUCKTYPE>
+
+With the ducktype option, you pass a ducktype type constraint object whose
+"interface" then becomes the list of methods to handle. The "interface" can be
+defined as; the list of methods passed to C<duck_type> to create a ducktype
+type constraint. For more information on C<duck_type> please check
+L<Moose::Util::TypeConstraint|Moose::Util::TypeConstraint>.
+
 =item C<CODE>
 
 This is the option to use when you really want to do something funky. You should