unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: srfi-18 and the vm
Date: Sun, 24 May 2009 16:08:20 +0200	[thread overview]
Message-ID: <87eiueegq3.fsf@gnu.org> (raw)
In-Reply-To: m3ljonsbvo.fsf@pobox.com

Hello,

Andy Wingo <wingo@pobox.com> writes:

> For loading uncompiled scripts, things will be slower, unless your
> modules #:use-syntax some other transformer. I don't know where the
> tradeoff is between the increased expansion speed due to compilation and
> slowdown due to a complete codewalk, but it's certainly there.

Yes.  Likewise, it may be reasonable to assume from now on that most of
the code will be compiled.  For instance, an uncompiled script may just
be a small code snipped that uses mostly compiled code.

> OTOH I would suspect that we can implement some kind of just-in-time
> compilation -- essentially for each use-modules we can check to see if
> the module is compiled, and if not just compile it then and there. It
> would be a little slow the first time, but after that it would load much
> faster, even faster than before. Python does this. We could add a guile
> --no-comp option to disable it.

I don't like this idea because it implies implicitly letting Guile
fiddle with the user's file system.  OTOH, it's a pragmatic approach to
the problem at hand.

Thanks,
Ludo'.





  reply	other threads:[~2009-05-24 14:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 14:39 srfi-18 and the vm Andy Wingo
2009-05-22 15:01 ` Julian Graham
2009-05-22 15:10 ` Ludovic Courtès
2009-05-22 16:20   ` Andy Wingo
2009-05-22 22:04     ` Ludovic Courtès
2009-05-23  9:52 ` Neil Jerram
2009-05-23 16:38   ` Andy Wingo
2009-05-23 22:03     ` Ludovic Courtès
2009-05-23 22:16       ` Andy Wingo
2009-05-24 14:08         ` Ludovic Courtès [this message]
2009-05-25 21:57           ` Neil Jerram
2009-05-29  9:55             ` Andy Wingo
2009-05-30 23:07               ` Neil Jerram
2009-05-31 13:30                 ` 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=87eiueegq3.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.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).