On Mon, 21 May 2001, Patrick Logan wrote:
> Would that Ruby borrowed Communicating Sequential Processes
> from Erlang. http://www.erlang.org
> I don't know about you, but I don't want to be programming with
> monitors and shared variables anymore. Java chose Hoare's monitor
> mechanism even though Hoare himself abandoned them for CSPs in
> the late 1970s.

I don't know much about Erlang but wouldn't it be much like each "thread" 
gets its event-loop, and each event-loop object doubles as a mailbox that
receives data from other "threads", and let that be the sole method of
communication between threads?

If "threads" are further isolated by deep-copying everything that passes
through the mailboxes, then it becomes only one step away from processes
at the OS-level: the decision between threads and processes becomes almost
aesthetics (or performance tuning).

Btw, I think I'll post my event loop pretty soon. People have asked for
it three weeks ago. I want to review the code first though.

matju