From: jnc@mercury.lcs.mit.edu (Noel Chiappa)
Subject: [TUHS] Happy birthday, Niklaus Wirth!
Date: Fri, 16 Feb 2018 08:42:43 -0500 (EST) [thread overview]
Message-ID: <20180216134243.62D8C18C098@mercury.lcs.mit.edu> (raw)
> From: Larry McVoy <lm at mcvoy.com>
> I don't know all the details but lisp and performance is not a thing.
This isn't really about Unix, but I hate to see inaccuracies go into
archives...
You might want to read:
http://multicians.org/lcp.html
Of course, when it comes to the speed/efficientcy of the compiled code, much
depends on the program/programmer. If one uses CONS wildly, there will have to
be garbage collection, which is of course not fast. But properly coded to stay
away from expensive constructs, my understanding is that 'lcp' and NCOMPLR
produced pretty amazing object code.
Noel
next reply other threads:[~2018-02-16 13:42 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-16 13:42 Noel Chiappa [this message]
2018-02-16 21:02 ` Tim Bradshaw
-- strict thread matches above, loose matches on Subject: below --
2018-02-18 20:50 Norman Wilson
2018-02-19 0:28 ` Dave Horsfall
[not found] <mailman.22.1518790085.20342.tuhs@minnie.tuhs.org>
2018-02-16 17:40 ` Paul McJones
2018-02-16 19:24 ` Bakul Shah
[not found] <mailman.1.1518746401.1018.tuhs@minnie.tuhs.org>
2018-02-16 2:40 ` Paul McJones
2018-02-16 2:19 Noel Chiappa
2018-02-16 2:48 ` Larry McVoy
2018-02-16 4:19 ` Steve Nickolas
2018-02-16 11:27 ` Tim Bradshaw
2018-02-16 15:45 ` Nemo
2018-02-14 21:06 Dave Horsfall
2018-02-14 21:12 ` Clem Cole
2018-02-14 22:15 ` George Michaelson
2018-02-14 23:37 ` Dave Horsfall
2018-02-14 21:24 ` Toby Thain
2018-02-16 0:01 ` Dave Horsfall
2018-02-16 0:51 ` Dan Cross
2018-02-16 1:06 ` Clem cole
2018-02-16 3:10 ` Toby Thain
2018-02-16 13:36 ` Clem Cole
2018-02-16 1:18 ` Larry McVoy
2018-02-16 1:55 ` George Michaelson
2018-02-16 1:56 ` Lawrence Stewart
2018-02-16 2:38 ` Dan Cross
2018-02-16 2:41 ` Larry McVoy
2018-02-16 2:51 ` Dan Cross
2018-02-16 2:56 ` George Michaelson
2018-02-16 10:26 ` Tim Bradshaw
2018-02-16 1:25 ` Ian Zimmerman
2018-04-24 0:59 ` Ian Zimmerman
2018-04-24 3:26 ` Dave Horsfall
2018-04-24 4:31 ` Dan Stromberg
2018-04-24 13:42 ` Clem Cole
2018-02-16 2:09 ` Bakul Shah
2018-02-16 2:31 ` Toby Thain
2018-02-16 10:01 ` Tim Bradshaw
2018-02-16 12:10 ` Bakul Shah
2018-02-16 12:37 ` tfb
2018-02-16 13:34 ` Bakul Shah
2018-02-16 14:07 ` Bakul Shah
2018-02-16 20:13 ` tfb
2018-02-16 3:17 ` Dan Stromberg
2018-02-14 23:19 ` Greg 'groggy' Lehey
2018-02-14 23:31 ` Dave Horsfall
2018-02-15 17:32 ` Steffen Nurpmeso
2018-02-15 19:18 ` Ian Zimmerman
2018-02-15 20:56 ` Steffen Nurpmeso
2018-02-15 21:31 ` Jeremy C. Reed
2018-02-15 2:30 ` Nemo
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=20180216134243.62D8C18C098@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).