Just Another Victim of the -spam trigger removed-t Morality wrote:
>     The problem is that dynamic typing, while very powerful, also hid 
> the
> intent of the method.  

For preventing the problem, my answer is the same as everyone else's...
Good naming techniques.

For figuring them out...  Unit Testing!  If it doesn't already have some
tests, write some.  As Francis said, you'll get some informative
messages back.  It's kind of a perversion of unit testing, but I often
use it to quickly experiment with classes I don't completely understand.
Once I can make working tests for something, I usually understand it
pretty well.  And I've always got them to look back at in case I forget
how I managed to make it work.  (Without hunting through tons of code.)

As for static typing...  I feel your pain.  It's heresy, but I prefer
static typing.  Inheritance provides everything I need that Duck Typing
does for me.  (At least, so far.  I'm really new to Ruby.)

-sigh- Victim, your name triggers the spam filter here.  Am I the only 
one annoyed by this?

-- 
Posted via http://www.ruby-forum.com/.