From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] lisp challenge
Date: Fri, 16 Feb 2018 18:44:32 -0500 (EST) [thread overview]
Message-ID: <20180216234432.75A2318C08F@mercury.lcs.mit.edu> (raw)
> From: Larry McVoy <lm at mcvoy.com>
> the proof here is to show up with a pure lisp grep that is fast as the C
> version. ... I've never seen a lisp program that out performed a well
> written C program.
Your exact phrase (which my response was in reply to) was "lisp and
performance is not a thing". You didn't say 'LISP is not just as fast as C' -
a different thing entirely. I disagreed with your original statement, which
seems to mean 'LISP doesn't perform well'.
Quite a few people spent quite a lot of time making LISP compiler output fast,
to the point that it was possible to say "this compiler is also intended to
compete with the S-1 Pascal and FORTRAN compilers for quality of compiled
numeric code" [Brooks,Gabriel and Steele, 1982] and "with the development of
the S-1 Lisp compiler, it once again became feasible to implement Lisp in Lisp
and to expect similar performance to the best hand-tuned,
assembly-language-based Lisp systems" [Steele and Gabriel, 1993].
Noel
next reply other threads:[~2018-02-16 23:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 23:44 Noel Chiappa [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-02-16 21:01 Larry McVoy
2018-02-16 21:03 ` Larry McVoy
2018-02-16 22:05 ` Bakul Shah
2018-02-16 22:28 ` Larry McVoy
2018-02-16 22:53 ` Donald ODona
2018-02-16 23:01 ` Arthur Krewat
2018-02-16 22:56 ` Arthur Krewat
2018-02-16 23:02 ` Larry McVoy
2018-02-16 23:18 ` Toby Thain
2018-02-16 23:41 ` Larry McVoy
2018-02-16 23:49 ` Bakul Shah
2018-02-16 23:34 ` Andy Kosela
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=20180216234432.75A2318C08F@mercury.lcs.mit.edu \
--to=jnc@mercury.lcs.mit.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).