9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: alef compiler
Date: Tue, 25 May 2004 01:42:09 +0100	[thread overview]
Message-ID: <ce33c69dc6267e9afe5e0804a948ba53@vitanuova.com> (raw)
In-Reply-To: <1085441730.20136.29.camel@kirschwenk>

> Even if it is a museum piece, if there is some interest wouldn't it be
> good thing to have the code out there?

i'm not sure that -code- is better than -no code-...

deleting code is a wonderful thing!

although i only used alef in passing, i did do a little bit of
exploring around the language, and the impression i got was that the
basics were there, but the vision had faltered somewhat towards the
end.

i think phil had had loads of ideas about what one might do with a
language, but not all of them were fully developed.  for instance, the
polymorphism support was substantially broken, so even if you had the
compiler, you'd still have to fix those bugs...

from my point of view, the basic problem with alef is that it tries to
be too much like C.

in a concurrent programming language, garbage collection and
language support for immutable complex types, such as you get in
limbo, make all the difference.

i'm not sure the distinction between threads and processes is a good
idea either.  it doesn't make for good modularity (no way of telling
if a function you're calling performs a communication or not; no way
of telling if your caller expects to remain in an atomic section).



  reply	other threads:[~2004-05-25  0:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-23 18:01 [9fans] " Matthew Swank
2004-05-24  6:58 ` [9fans] " Russ Cox
2004-05-24 18:01   ` Matthew Swank
2004-05-24 23:04   ` Latchesar Ionkov
2004-05-24 23:24     ` Russ Cox
2004-05-25  1:53     ` boyd, rounin
2004-05-24 23:35   ` Matthew Swank
2004-05-25  0:42     ` rog [this message]
2004-05-25 14:29       ` Jeff Sickel
2004-05-25 14:42         ` rog
2004-05-25 17:51           ` boyd, rounin
2004-05-25 17:56             ` Fco. J. Ballesteros
2004-05-25  0:07 dmr

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ce33c69dc6267e9afe5e0804a948ba53@vitanuova.com \
    --to=rog@vitanuova.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).