unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Wilfred Hughes <me@wilfred.me.uk>
To: 24363@debbugs.gnu.org
Subject: bug#24363: Acknowledgement (Clarify the VM docs)
Date: Sun, 4 Sep 2016 01:08:07 -0400	[thread overview]
Message-ID: <CAFXAjY7j1eLEQZZQP10k5oOLJDHV02tO-NxLFLEMy8n=NMii4g@mail.gmail.com> (raw)
In-Reply-To: <handler.24363.B.147296552715192.ack@debbugs.gnu.org>


[-- Attachment #1.1: Type: text/plain, Size: 942 bytes --]

Here's my proposed change as a patch against master, currently
cb421b6546ad3e09299462df63c389aa734fdba8.

On 4 September 2016 at 01:06, GNU bug Tracking System <help-debbugs@gnu.org>
wrote:

> Thank you for filing a new bug report with debbugs.gnu.org.
>
> This is an automatically generated reply to let you know your message
> has been received.
>
> Your message is being forwarded to the package maintainers and other
> interested parties for their attention; they will reply in due course.
>
> Your message has been sent to the package maintainer(s):
>  bug-guile@gnu.org
>
> If you wish to submit further information on this problem, please
> send it to 24363@debbugs.gnu.org.
>
> Please do not send mail to help-debbugs@gnu.org unless you wish
> to report a problem with the Bug-tracking system.
>
> --
> 24363: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=24363
> GNU Bug Tracking System
> Contact help-debbugs@gnu.org with problems
>

[-- Attachment #1.2: Type: text/html, Size: 1709 bytes --]

[-- Attachment #2: vm_docs.patch --]
[-- Type: text/x-patch, Size: 1071 bytes --]

diff --git a/doc/ref/vm.texi b/doc/ref/vm.texi
index 2f32c51..9766ccb 100644
--- a/doc/ref/vm.texi
+++ b/doc/ref/vm.texi
@@ -62,10 +62,12 @@ The obvious solution is to compile to a virtual machine that is
 present on all Guile installations.
 
 The easiest (and most fun) way to depend on a virtual machine is to
-implement the virtual machine within Guile itself. This way the
-virtual machine provides what Scheme needs (tail calls, multiple
-values, @code{call/cc}) and can provide optimized inline instructions
-for Guile (@code{cons}, @code{struct-ref}, etc.).
+implement the virtual machine within Guile itself. Guile contains a
+bytecode interpreter (written in C) and a Scheme to bytecode compiler
+(written in Scheme). This way the virtual machine provides what Scheme
+needs (tail calls, multiple values, @code{call/cc}) and can provide
+optimized inline instructions for Guile (@code{cons}, @code{struct-ref},
+etc.).
 
 So this is what Guile does. The rest of this section describes that VM
 that Guile implements, and the compiled procedures that run on it.

  parent reply	other threads:[~2016-09-04  5:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04  5:04 bug#24363: Clarify the VM docs Wilfred Hughes
     [not found] ` <handler.24363.B.147296552715192.ack@debbugs.gnu.org>
2016-09-04  5:08   ` Wilfred Hughes [this message]
2016-09-04 16:14     ` bug#24363: Acknowledgement (Clarify the VM docs) Andy Wingo
2016-09-05  0:23       ` Wilfred Hughes
2016-09-05 18:52         ` Andy Wingo
2017-03-01  9:07           ` 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='CAFXAjY7j1eLEQZZQP10k5oOLJDHV02tO-NxLFLEMy8n=NMii4g@mail.gmail.com' \
    --to=me@wilfred.me.uk \
    --cc=24363@debbugs.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).