From: Kevin Ryde <user42@zip.com.au>
To: ludo@chbouib.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: Evolution & optimization of the module system
Date: Tue, 27 Feb 2007 09:46:03 +1100 [thread overview]
Message-ID: <87zm70fsgk.fsf@zip.com.au> (raw)
In-Reply-To: <87fy8shb8l.fsf@chbouib.org> (Ludovic Courtès's message of "Mon, 26 Feb 2007 22:15:06 +0100")
ludo@chbouib.org (Ludovic Courtès) writes:
>
> Writing in C or assembly doesn't free from choosing appropriate
> algorithms.
It's rather unfair to the data structure to say it's no good when
there's likely to be an easy speedup between perhaps 2x and 5x. In
principle all core primitives should be implemented in C; it loads
faster, runs faster, and shares memory between processes. Of course
scheme is much friendlier to write, and there's no burning need to
squeeze out every last drop from things that are adequate as they
stand. But if there's an issue of performance then some C is the
natural first step (or natural first to be excluded).
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-02-26 22:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-17 15:15 Evolution & optimization of the module system Ludovic Courtès
2007-02-18 23:32 ` Kevin Ryde
2007-02-19 9:24 ` Ludovic Courtès
2007-02-21 22:21 ` Kevin Ryde
2007-02-22 9:20 ` Ludovic Courtès
2007-02-22 22:23 ` Kevin Ryde
2007-02-23 13:15 ` Ludovic Courtès
2007-02-25 23:37 ` Kevin Ryde
2007-02-26 21:15 ` Ludovic Courtès
2007-02-26 22:46 ` Kevin Ryde [this message]
2007-02-27 8:21 ` Ludovic Courtès
2007-04-08 23:06 ` Ludovic Courtès
2007-04-08 23:25 ` Ludovic Courtès
2007-04-08 23:24 ` Ludovic Courtès
2007-04-30 8:39 ` Ludovic Courtès
2007-05-05 20:48 ` Ludovic Courtès
2010-07-20 21:20 ` Andy Wingo
2010-07-20 22:24 ` Ludovic Courtès
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zm70fsgk.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=guile-devel@gnu.org \
--cc=ludo@chbouib.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 read-only IMAP folder(s) and NNTP newsgroup(s).