The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] lisp challenge
Date: Fri, 16 Feb 2018 17:56:59 -0500	[thread overview]
Message-ID: <8a4ac448-9ed2-016a-6440-33597e36915d@kilonet.net> (raw)
In-Reply-To: <20180216222835.GC27574@mcvoy.com>

Has ANY language (except assembler) EVER outperformed C in a big way?

Give or take any optimizations that may be done by either?

On 2/16/2018 5:28 PM, Larry McVoy wrote:
> I'm no lisp expert, not by any stretch, but I've never seen a lisp
> program that out performed a well written C program.



  parent reply	other threads:[~2018-02-16 22:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2018-02-16 23:44 Noel Chiappa

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=8a4ac448-9ed2-016a-6440-33597e36915d@kilonet.net \
    --to=krewat@kilonet.net \
    /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).