Ben Giddings wrote:

> Among people who don't program Ruby, one of the biggest complaints I've 
> heard is that they'd be scared to create a really big program in Ruby 
> because it wouldn't find a simple typo until it is actually executing 
> the code at that point.  If it's a rarely-hit spot, then it could be a 
> long time before it is discovered.  This concerns me too -- but I'm a 
> big enough fan that I overlook this flaw and use Ruby anyhow.

A code coverage tool (combined with unit tests) can help this. There's
one in RAA.


Hal