Lex Spoon wrote:
> 
> "Jim Benson" <jb at speed.net> wrote:
> > Lex,

> > In some sense, I get the feeling that I need (at the very least) a coding
> > equivalent to a word processor. A word processor checks for spelling and
> > grammatical mistakes, so should my development tools but in a different
> > context. It has to compile it of course, but it should also do lint checking
> > and make sure I don't make the 10 stupid Smalltalk mistakes. Ideally it
> > would know other thing too. Like when I've made algorithmic errors ( On2 vs
> > On for example ) , knows of a better algorithm than the one I'm using, or
> > has a better 'pattern' for some spot of code, but obviously all that's
> > somewhere down the road.
> 
> Of course, this isn't just UI changes -- there is  significant
> technology required to find an error in an algorithm!

The MethodFinder finds algorithms allready in the image. Could be fun to
integrate that ability into a code pane, to write what you want as 
a result instead of how to get it. 

Karl