From: andrey mirtchovski <mirtchov@cpsc.ucalgary.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Let's get functional?
Date: Tue, 8 Apr 2003 09:38:50 -0600 [thread overview]
Message-ID: <Pine.LNX.4.44.0304080930060.5973-100000@fbsd.cpsc.ucalgary.ca> (raw)
In-Reply-To: <497ecf2c9668c60cc22f5f384f8a9759@plan9.bell-labs.com>
On Tue, 8 Apr 2003, Russ Cox wrote:
> moscow ml is in /n/sources/extra. maybe that's what you meant by
> lisp-like languages, but if so neither the ml nor the lisp people would
> agree with you.
Haskell is in the same ballpark with ML, but has a somewhat bigger
following. I admit I didn't think of ML when I asked the question, but
seeing how often it is used within Plan9 (outside bell-labs at least) pretty
much answers my question about needing to bring yet another functional
language here...
andrey
next prev parent reply other threads:[~2003-04-08 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-08 7:14 andrey mirtchovski
2003-04-08 7:38 ` Richard Miller
2003-04-08 21:37 ` a
2003-04-08 15:13 ` Russ Cox
2003-04-08 15:38 ` andrey mirtchovski [this message]
2003-04-08 15:52 ` Russ Cox
2003-04-08 16:27 ` Dan Cross
2003-04-08 21:59 ` George Bronnikov
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=Pine.LNX.4.44.0304080930060.5973-100000@fbsd.cpsc.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).