threads - use them as much as you can

[Karlsson Mikael]

Luke Gorrie <luke@REDACTED> writes
.
.
> Samuel Tardieu <sam@REDACTED> writes:
> 
> > At the beginning of OO programming, programmers were told "Look, it is
> > so nice, you do not call subprograms, you send messages to objects which
> > will then react to those messages". This view was flawed, as the object
> > was not reacting at all (it had no thread of control on its own), it just
> > provided the caller with what to do (the method's code).
> 
> Somewhere between the two, Eiffel has (at least on paper) a really
> interesting CSP-like way of doing communication. I can't help but talk
> about it every time concurrency comes up.
.
.
> Cheers,
> Luke
> 
Talking about other languages..
O'Haskell is an attempt to extend a functional language, Haskell, with
object-orientation and concurrency. See:
http://www.cs.chalmers.se/~nordland/ohaskell/

/Mikael