[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: Coroutines and Go
- From: David Given <dg@...>
- Date: Thu, 12 Nov 2009 16:55:38 +0000
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Jim Whitehead II wrote:
[...]
> The PAR keyword doesn't in any way approximate 'OCCAM-like'
> concurrency. Concurrency in occam is built around communication
> between distinct processes through explicit communication channels.
> Yes, the SEQ keyword is covered by the sequential nature of Algol-68,
> and the PAR keywords are roughly the same.. but that only begins to
> graze the surface of what OCCAM-like concurrency actually is.
Indeed, you're quite right. I did meant to mention channels, honest, but
forgot. CSP concurrency is one of Go's nicer features.
...according to Wikipedia CSP was first described in a paper in 1978;
Occam came out in 1983 (although it looks way older from the syntax).
Perhaps Algol-68 simply predates it, which would explain why it has par
but no channels. Anyone modernising the language would definitely need
to add them.
- --
┌─── dg@cowlark.com ───── http://www.cowlark.com ─────
│ "There is nothing in the world so dangerous --- and I mean *nothing*
│ --- as a children's story that happens to be true." --- Master Li Kao,
│ _The Bridge of Birds_
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAkr8PgcACgkQf9E0noFvlzhGvgCcDhLQatJUfUhW6KVRWFMf+PTV
u/wAnjbOWm/dchOgWfjox7seJd5dx0Dk
=v1QI
-----END PGP SIGNATURE-----