[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Guile-commits] 01/01: Clarify bootstrap docs

From: Andy Wingo
Subject: [Guile-commits] 01/01: Clarify bootstrap docs
Date: Mon, 5 Sep 2016 18:50:41 +0000 (UTC)

wingo pushed a commit to branch master
in repository guile.

commit 605a01bfceebf19a7f5ce17500ca82eeefe40fee
Author: Wilfred Hughes <address@hidden>
Date:   Sun Sep 4 20:14:49 2016 -0400

    Clarify bootstrap docs
    * doc/ref/vm.texi: Add a sentence stating which parts of the bytecode
      toolchain are in C, and which are in Scheme. This avoids confusion if
      users assume Guile==Scheme and so assume the whole toolchain is in
 doc/ref/vm.texi |   10 ++++++----
 1 file changed, 6 insertions(+), 4 deletions(-)

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},
 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]