From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu, matt@lanl.gov
Subject: Re: [9fans] haskell for plan9 (fwd)
Date: Mon, 21 Apr 2003 18:05:52 -0400 [thread overview]
Message-ID: <d857e6078bcc6593ed7e6bb0e605d0d2@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304211549500.18914-100000@maxroach.lanl.gov>
There was an SML/NJ port long ago, but SML and
Plan 9 both evolved and it wasn't kept up-to-date.
SML knows a lot about the underlying system -- things
like register calling conventions and the like -- so it's
quite a job to port it.
I believe these are the same reasons that the GHC
compiler was said to be too hard to port.
Moscow ML, which is SML2000 compliant, has been
ported and is on the updates page. It's a byte-code
interpreter, like Hugs, and was thus similarly easy
to port.
Russ
next prev parent reply other threads:[~2003-04-21 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-21 21:50 ron minnich
2003-04-21 22:05 ` Russ Cox [this message]
2003-04-22 2:17 ` [9fans] haskell for plan9 andrey mirtchovski
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=d857e6078bcc6593ed7e6bb0e605d0d2@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
--cc=matt@lanl.gov \
/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).