unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Neil Jerram" <neiljerram@googlemail.com>
To: "Andy Wingo" <wingo@pobox.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: vm branch now uses vm repl by default
Date: Wed, 10 Sep 2008 00:43:39 +0200	[thread overview]
Message-ID: <49dd78620809091543j2a811a01lffe13d9be3c6ee7d@mail.gmail.com> (raw)
In-Reply-To: <m38wu195m5.fsf@pobox.com>

2008/9/9 Andy Wingo <wingo@pobox.com>:
>
>    Sources:
>
>       8    #(1 11 #f)
>
> Some instructions are annotated with source information.

I guess source information is of interest for debugging, and I think
you've observed previously elsewhere that the VM doesn't yet have much
debugging support - by which I presume you mean something like the
traps that the evaluator has.

So I was just wondering if we actually _need_ any debugging support in
the VM.  If we can assume that the VM will always behave equivalently
to the evaluator (except faster), then whenever a piece of code needs
step-by-step debugging, the developer can drop back to using the
evaluator in order to do that.

Does that make sense?

(Then another question is whether we can assume that the VM behaves
equivalently to the evaluator.  I wonder if there is some test
methodology for partly proving this, by automatically running the
evaluator in parallel with the VM, at least for code that doesn't have
side effects?

I'm sorry, this email has ended up a bit vague....)

      Neil




  parent reply	other threads:[~2008-09-09 22:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-09  6:48 vm branch now uses vm repl by default Andy Wingo
2008-09-09  8:27 ` Neil Jerram
2008-09-09 17:59   ` Andy Wingo
2008-09-09 22:27     ` Neil Jerram
2008-09-09  8:41 ` Ludovic Courtès
2008-09-09 18:13   ` Andy Wingo
2008-09-09 21:01     ` Ludovic Courtès
2008-09-10 19:05       ` Andy Wingo
2008-09-09 22:43 ` Neil Jerram [this message]
2008-09-10 18:51   ` Andy Wingo
2008-09-10 21:24     ` Neil Jerram

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=49dd78620809091543j2a811a01lffe13d9be3c6ee7d@mail.gmail.com \
    --to=neiljerram@googlemail.com \
    --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).