From: Simon Strandgaard <neoneye@...>
Date: 2004-05-20T02:38:56+09:00
Subject: Re: How to duck type? - the psychology of static typing in Ruby

Ben Giddings wrote:
[snip]
> > 
> > jenova ~ % cat -n what.pl
> >      1  $num = 3;
> >      2  $num += 2;
> >      3  if ($numb != 5) {
> >      4       print "Foo!!\n";
> >      5  }
> > jenova ~ % perl -cw what.pl
> > Name "main::numb" used only once: possible typo at what.pl line 3.
> > what.pl syntax OK
> 
> At no point does it try to run the code, but it still finds that 
> potential trouble spot.
> 
> I think unit tests are great, so are code coverage tools, as are 
> profilers and debuggers... but I still see a need for 'typo catchers'.

Have a look at this sample output.. its amazing what this tool are able
to figure out about your code.
http://pag.csail.mit.edu/daikon/StackAr.html

My wishlist of useful Ruby-tool are ever growing.

-- 
Simon Strandgaard