On Sat, Aug 09, 2003 at 08:29:24AM +0900, Jim Weirich wrote:
> Duck typing itself has little to do with using responds_to?. Duck
> typing is what we do every day in Ruby where we don't explicitly declare
> types by inheriting from a classes or interfaces. We just implement the
> methods needed (with the proper semantics).
>
> The responds_to? thread has more to do with type discovery
Just as an aside, it's respond_to? not responds_to?
(like Array#include? not being Array#includes?)
Cheers,
Brian.