unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Neil Jerram <neil@ossau.uklinux.net>
To: Andy Wingo <wingo@pobox.com>
Cc: "Ludovic Courtès" <ludo@gnu.org>, guile-devel@gnu.org
Subject: Re: data-crunching in guile
Date: Fri, 26 Jun 2009 22:25:04 +0100	[thread overview]
Message-ID: <874ou2lmbz.fsf@arudy.ossau.uklinux.net> (raw)
In-Reply-To: <m3ws6zkqm1.fsf@pobox.com> (Andy Wingo's message of "Fri\, 26 Jun 2009 16\:37\:58 +0200")

Andy Wingo <wingo@pobox.com> writes:

> Hi Neil!

Hi Andy!

> On Fri 26 Jun 2009 00:47, Neil Jerram <neil@ossau.uklinux.net> writes:
>
>> Thanks, I see now.  But presumably even VM code will frequently call
>> out to primitives all over libguile, won't it?
>
> Over time, I'd say no. I see functions written in C migrating over to be
> written in Scheme, like PLT did recently with `map'. We should port
> srfi-1 back to Scheme I think :) Not to mention silly things like
> string-any being in boot-9...
>
> There's no reason for Scheme to be slow. Of course, this is the "over
> time" view, currently we're not there...
>
> And yet, disassemble the functions that you use regularly, and often you
> find they just use VM ops, and don't call out to primitives. That shows
> that the VM is, while virtual, still quite a good machine for
> computation.

Fair enough, I can see that now.  In other words, that there will be
long enough passages of pure VM code to make the VM code size important.

    Neil




  reply	other threads:[~2009-06-26 21:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-24 12:03 data-crunching in guile Andy Wingo
2009-06-25  7:26 ` Neil Jerram
2009-06-25  8:04 ` Ludovic Courtès
2009-06-25 21:08   ` Andy Wingo
2009-06-25 22:47     ` Neil Jerram
2009-06-26 14:37       ` Andy Wingo
2009-06-26 21:25         ` Neil Jerram [this message]
2009-06-26 12:09 ` Andy Wingo

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=874ou2lmbz.fsf@arudy.ossau.uklinux.net \
    --to=neil@ossau.uklinux.net \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=wingo@pobox.com \
    /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).