From: Lyle Johnson Date: 2006-08-22T21:50:57+09:00 Subject: Re: Static typing ain't so bad, after all... On 8/22/06, Just Another Victim of the Ambient Morality wrote: > Has anyone noticed this? How do you deal with this issue? Most of the time I'm able to deduce what kind of object the method is expecting, but I agree that sometimes I have to do a lot of detective work to find out how to use the code. If an object is passed in to a method, and is *only* used within that method, it's usually straightforward to just use the duck typing assumption: I just need to pass in some object that's capable of responding to the messages that will be sent to it in this context. But what if the object is passed down into some other method as an argument? Or stored in an instance variable for later use? In those situations, I have to chase that rabbit all around the code, seeing how it's used elsewhere, before I can know for sure what kind of object I need to provide. It's definitely a documentation issue, in my book. But I'm looking forward to other responses.