From: Matthew Swank <akopa@comcast.net>
To: Russ Cox <russcox@gmail.com>
Cc: 9fans <9fans@cse.psu.edu>
Subject: [9fans] Re: alef compiler
Date: Mon, 24 May 2004 18:35:31 -0500 [thread overview]
Message-ID: <1085441730.20136.29.camel@kirschwenk> (raw)
In-Reply-To: <ee9e417a04052323587c53654d@mail.gmail.com>
Well, you called my bluff. I don't think I am up for anything as
ambitious as releasing Limbo from the Inferno, so I'll just take my
alef2c translator and go home.
Seriously, though, Alef seems to have gotten lost because no-one
(important) thought it was worth the trouble to continue to support it.
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 for one would be grateful to
have the opportunity to hack on it.
Matt
next prev parent reply other threads:[~2004-05-24 23:35 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 [this message]
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=1085441730.20136.29.camel@kirschwenk \
--to=akopa@comcast.net \
--cc=9fans@cse.psu.edu \
--cc=russcox@gmail.com \
/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).