From: Dan Cross <crossd@gmail.com>
To: gdiaz@qswarm.com
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] sml/nj and unix/plan9
Date: Thu, 7 May 2020 13:40:26 -0400 [thread overview]
Message-ID: <CAEoi9W5S0TZWT4MOuePr7q9+rthP8Xu7y1CZWUi_bGt77J9tXg@mail.gmail.com> (raw)
In-Reply-To: <3740275.SCiKnK0d8l@slayer.slackware.es>
[-- Attachment #1: Type: text/plain, Size: 993 bytes --]
On Mon, May 4, 2020 at 8:49 AM <gdiaz@qswarm.com> wrote:
> Was sml/nj part of UNIX at some point? was it considered as a language to
> use
> (proof tools may be)?
>
> I was wondering if there is any history in common between the two. I've
> been
> unable to find anything :-?, please share your stories! :-D
>
There was certainly proximity, if not a direct connection.
Is it true that the language was too slow to be generally useful? There
> seems
> to be commentaries along these lines on the internet.
>
This question is difficult to answer. As a _langage_ there's little that
makes SML inherently slow; the MLton compiler does full-program
optimization with advanced optimizations and generates code that's pretty
performant. There are certainly other SML implementations that generate
slow code; MoscowML comes to mind: it generates a byte code that's not
known for speed. SML/NJ is pretty zippy, but I've never tried to write
anything performance-critical with it.
- Dan C.
[-- Attachment #2: Type: text/html, Size: 1524 bytes --]
next prev parent reply other threads:[~2020-05-07 17:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-04 12:39 gdiaz
2020-05-07 14:58 ` Andrew Koenig
2020-05-07 17:40 ` Dan Cross [this message]
2020-05-07 20:47 ` A. P. Garcia
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=CAEoi9W5S0TZWT4MOuePr7q9+rthP8Xu7y1CZWUi_bGt77J9tXg@mail.gmail.com \
--to=crossd@gmail.com \
--cc=gdiaz@qswarm.com \
--cc=tuhs@tuhs.org \
/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).