9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Russ Cox <russcox@gmail.com>
To: Matthew Swank <akopa@comcast.net>, 9fans <9fans@cse.psu.edu>
Subject: [9fans] Re: alef compiler
Date: Mon, 24 May 2004 02:58:48 -0400	[thread overview]
Message-ID: <ee9e417a04052323587c53654d@mail.gmail.com> (raw)
In-Reply-To: <1085335289.18040.18.camel@kirschwenk>

We could probably get the lawyers to okay releasing the Alef code,
but I don't see the good it would do.  The Alef compilers
generate Plan 9 object files, which, as discussed in the
archives, are quite different beasts from standard Unix
object files.  Further, if you really want to coexist on Unix, you
don't want to be in the business of generating your own
object files.  I suppose you could retrofit the Alef compilers
to pipe assembly into as.

Libthread provides almost all the run-time support of Alef.
It would likely not be hard to write a front end that translated
Alef code into C+libthread, but it's even easier just to write
in C to begin with, since all the Alef base has been converted.
The differences between Alef and C+libthread are almost entirely
syntactic.  I miss the syntax when I use channels, but I don't miss
it enough to make it seem worthwhile to maintain a converter.

On my list of ideal changes to my programming environment,
Alef syntax isn't very high.  I'd much rather see better support
for profiling, debugging, garbage collection, and automatically
checking correctness.

I think making Limbo run on Unix is a lot more interesting than
making Alef run on Unix.  If anyone wants to try that, I'd be
happy to provide code and moral support.

Just my opinion.

Russ


  reply	other threads:[~2004-05-24  6:58 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 ` Russ Cox [this message]
2004-05-24 18:01   ` [9fans] " 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
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=ee9e417a04052323587c53654d@mail.gmail.com \
    --to=russcox@gmail.com \
    --cc=9fans@cse.psu.edu \
    --cc=akopa@comcast.net \
    /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).