Bob La Quey wrote:
So do you have an alternative?
Alternative to what?
Or a higher level language you would suggest?
Erlang. Gambit with Termite. Scala and Actors. Pick one.
All of these use Actors/Message Passing but still allow higher level
programming constructs for the sequential sections. In addition, the
Actors/Message Passing model for concurrency is not exactly new.
The immutability of variables combined with message passing and pattern
matched tail calls creates some very nice state machine constructs in
Erlang. This is unsurprising given that Erlang was created for
networking hardware.
Shared transactional memory and Haskell seem to be generating some
papers, but some people have shown that transactions don't compose as
nicely as originally believed.
My primary beef with Erlang is the fact that only one VM exists (I have
a bit of problem about the weak REPL, but I can ignore that). Until you
have two separate implementations of a language (two different
compilers, two different interpreters, or two different VM's), the
ability of that language to adapt to new hardware, operating systems, or
environments is unknown.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
