unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: No Itisnt <theseaisinhere@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: [PATCH] Update docs to reflect new external representation of tree-il <letrec>
Date: Fri, 13 Aug 2010 15:18:35 -0500	[thread overview]
Message-ID: <AANLkTi=+DUk_hKPqKfJvWPs7oErxmN4zqXf-G_YSx4QW@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 180 bytes --]

That was funny, just spent an hour trying to figure out what was wrong
with my letrec when it was really that there's no explicit in-order?
in the external representation anymore.

[-- Attachment #2: 0001-Update-documentation-to-reflect-new-tree-il-external.patch --]
[-- Type: application/octet-stream, Size: 2064 bytes --]

From dffe1d6e5bd03b355f7192f69970dbf6bdacb08e Mon Sep 17 00:00:00 2001
From: No Itisnt <theseaisinhere+git@gmail.com>
Date: Fri, 13 Aug 2010 15:13:25 -0500
Subject: [PATCH] Update documentation to reflect new tree-il external representation for <letrec>.

* doc/ref/compiler.texi: That thing I just said
---
 doc/ref/compiler.texi |   17 +++++++++--------
 1 files changed, 9 insertions(+), 8 deletions(-)

diff --git a/doc/ref/compiler.texi b/doc/ref/compiler.texi
index 494a676..d28ce0f 100644
--- a/doc/ref/compiler.texi
+++ b/doc/ref/compiler.texi
@@ -20,12 +20,12 @@ curtain.
 know how to compile your @code{.scm} file.
 
 @menu
-* Compiler Tower::                   
-* The Scheme Compiler::                   
-* Tree-IL::                 
-* GLIL::                
-* Assembly::                   
-* Bytecode and Objcode::                   
+* Compiler Tower::
+* The Scheme Compiler::
+* Tree-IL::
+* GLIL::
+* Assembly::
+* Bytecode and Objcode::
 * Writing New High-Level Languages::
 * Extending the Compiler::
 @end menu
@@ -84,7 +84,7 @@ scheme@@(guile-user)> ,language tree-il
 Happy hacking with Tree Intermediate Language!  To switch back, type `,L scheme'.
 tree-il@@(guile-user)> ,L scheme
 Happy hacking with Scheme!  To switch back, type `,L tree-il'.
-scheme@@(guile-user)> 
+scheme@@(guile-user)>
 @end example
 
 Languages can be looked up by name, as they were above.
@@ -442,7 +442,8 @@ original binding names, @var{gensyms} are gensyms corresponding to the
 @var{exp} is a single Tree-IL expression.
 @end deftp
 @deftp {Scheme Variable} <letrec> in-order? src names gensyms vals exp
-@deftpx {External Representation} (letrec @var{in-order?} @var{names} @var{gensyms} @var{vals} @var{exp})
+@deftpx {External Representation} (letrec @var{names} @var{gensyms} @var{vals} @var{exp})
+@deftpx {External Representation} (letrec* @var{names} @var{gensyms} @var{vals} @var{exp})
 A version of @code{<let>} that creates recursive bindings, like
 Scheme's @code{letrec}, or @code{letrec*} if @var{in-order?} is true.
 @end deftp
-- 
1.7.2.1


             reply	other threads:[~2010-08-13 20:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-13 20:18 No Itisnt [this message]
2010-08-27 16:17 ` [PATCH] Update docs to reflect new external representation of tree-il <letrec> 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='AANLkTi=+DUk_hKPqKfJvWPs7oErxmN4zqXf-G_YSx4QW@mail.gmail.com' \
    --to=theseaisinhere@gmail.com \
    --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).