From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Let's get functional?
Date: Tue, 8 Apr 2003 11:13:59 -0400 [thread overview]
Message-ID: <497ecf2c9668c60cc22f5f384f8a9759@plan9.bell-labs.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0304080105350.5203-100000@fbsd.cpsc.ucalgary.ca>
> The language that I had in mind is Haskell. I can't figure out a way Haskell
> could fit nicely with the Plan9 paradigms (everything is a file, private
> namespaces, etc), but, say, a haskell->draw() module could be of some use...
> somewhat...
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.
next prev parent reply other threads:[~2003-04-08 15:13 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 [this message]
2003-04-08 15:38 ` andrey mirtchovski
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=497ecf2c9668c60cc22f5f384f8a9759@plan9.bell-labs.com \
--to=rsc@plan9.bell-labs.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).