From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [VM] Tail recursion and multiple values
Date: Mon, 02 Mar 2009 00:48:22 +0100 [thread overview]
Message-ID: <87y6vox0s9.fsf@gnu.org> (raw)
In-Reply-To: m363itkms8.fsf@pobox.com
Hello!
Andy Wingo <wingo@pobox.com> writes:
> On Sat 28 Feb 2009 15:45, ludo@gnu.org (Ludovic Courtès) writes:
>> Actually no: it works with VM-compiled code, but it breaks when using
>> Guile-VM with `,o interp #t' (which appears to be the default, except at
>> the REPL).
>
> This is a misunderstanding.
>
> Last things first: code is not run through the VM unless it is compiled.
> The REPL in the vm branch compiles expressions by default, though it has
> an option to use the interpreter instead (,option interp #t).
Understood.
> So what I really mean to say is:
>
> 1) It is expected that you don't have tail recursion between
> interpreted and VM code.
>
> 2) This particular problem manifests itself in that call-with-values
> is VM code (when r5rs.scm is compiled).
(The latter is what I meant to say in my message.)
As for (1), I'm unsure. The issue is that as long as running code with
the interpreter is the default, people may hit this kind of problem,
which is, well, problematic. Now, I have no idea how this could be
solved without resorting to dirty hacks such as the one you suggested.
As a side note, I think it makes sense to keep the interpreter as the
default when evaluating `.scm' files since compilation can be costly and
may not pay off (e.g., if the compiler performs smart optimizations,
and/or the program is short-lived).
Thanks,
Ludo'.
next prev parent reply other threads:[~2009-03-01 23:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 14:27 [VM] Tail recursion and multiple values Ludovic Courtès
2009-02-28 14:45 ` Ludovic Courtès
2009-03-01 20:31 ` Andy Wingo
2009-03-01 23:48 ` Ludovic Courtès [this message]
2009-03-02 18:03 ` Andy Wingo
2009-03-02 21:55 ` Ludovic Courtès
2009-03-02 23:15 ` Andy Wingo
2009-03-02 23:33 ` Andreas Rottmann
2009-03-02 23:43 ` Eduardo Cavazos
2009-03-03 23:45 ` Ludovic Courtès
2009-03-04 22:11 ` Clinton Ebadi
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=87y6vox0s9.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).