unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: SRFI-1 in Scheme
Date: Wed, 14 Jul 2010 00:44:17 +0200	[thread overview]
Message-ID: <87sk3nt326.fsf@gnu.org> (raw)
In-Reply-To: <m3tyo381au.fsf@unquote.localdomain> (Andy Wingo's message of "Wed, 14 Jul 2010 00:27:53 +0200")

Hey,

Andy Wingo <wingo@pobox.com> writes:

> On Wed 14 Jul 2010 00:09, ludo@gnu.org (Ludovic Courtès) writes:

>> AFAICS the only difference between the two engine is VM_USE_HOOKS.
>> Hooks are only used in (system vm coverage) at this point, so we don’t
>> lose much by disabling them.
>
> Tracing and call-counting profiling too. They will be used when stepping soon.

Right.

To clarify, I’d enable the debug engine for interactive use, but not for
‘-s’, ‘-c’, and when a script is passed as an argument (analogous to
what 1.8 does with the evaluators.)

Tracing and stepping are typically only used interactively, so that’s
OK.  Coverage and profiling can start a new VM that suits their needs,
à la ‘with-code-coverage’.

So my impression is that the behavior above would usually have no
drawbacks for the end user, in that it wouldn’t visibly reduce
functionality.

What do you think?

Thanks,
Ludo’.



  reply	other threads:[~2010-07-13 22:44 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-12 22:57 SRFI-1 in Scheme Ludovic Courtès
2010-07-13 21:25 ` Andy Wingo
2010-07-13 22:09   ` Ludovic Courtès
2010-07-13 22:27     ` Andy Wingo
2010-07-13 22:44       ` Ludovic Courtès [this message]
2010-07-14  7:41         ` Andy Wingo
2010-07-15 21:40           ` Ludovic Courtès
2010-07-19 20:30             ` Andy Wingo
2010-07-20 16:35               ` Ludovic Courtès
2010-07-20 20:11                 ` Andy Wingo
2010-07-21 23:10                   ` Ludovic Courtès
2010-07-20 20:15                 ` Andy Wingo
2010-09-01 16:04               ` Allowing the choice of a VM engine? Ludovic Courtès
2010-09-03  5:23                 ` 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=87sk3nt326.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@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).