Igor,

> >   Another approach to solve this problem is to make the editor
> > smarter.  I could imagine to have a some command-key sequence that
> > puts open and close parenthesis around the *last* expression.  The
> > definition of the "last" expression may need a clarification but it
> > almost sounds like "right before the last statement separater ($.)"
> > would be good.  With it, if you type:
> >
> >   aCollection select: [:each | each isSomething]
> >
> > and then realize that you actually want to continue to write collect:,
> > then you press a key combination and it enclose the above expression
> > with $( and $).  In this way, you don't have to change the language.
> >
> >   For this kind of stuff, having three different precedence in message
> > sending is basically two too many.  That is why the lisp-mode in Emacs
> > shines more than any other modes.  But for Smalltalk-80 syntax, it
> > wouldn't be too bad.
> >
> 
> And then the only thing you need is to implant a chip into your brain
> to be able read code with many (...) fast :)

  A proper indentation helps, of course.

  Prof. Takeuchi, a Lisp guru and known as the inventor of the "tak"
function, is also full of sense of humor.  One of his jokes takes a
form of dialog between a Lisp Master and a young apprentice of his:

  Apprentice: Master, there are too many parenthesis in this language!
              Even my eyes hurt! How could you write a program in it?

 Lisp Master: Huh? What parenthesis?  ... Ah, I totally forgot about
              them.

-- Yoshiki