From: ebuy <rtfds@online.de>
To: bug-guile@gnu.org
Subject: typo/bug in guile-bf08e10/doc/ref/api-control.texi
Date: Fri, 03 Sep 2010 23:47:08 +0200 [thread overview]
Message-ID: <1283550428.7803.20.camel@melody> (raw)
[-- Attachment #1: Type: text/plain, Size: 482 bytes --]
Hi,
maybe I'm wrong, but I consider the order "(PROC CONT)" in the
documentation of the procedure
"call-with-current-continuation"
in file guile-bf08e10/doc/ref/api-control.texi of the git-repository a
bug
Shouldn't that be transposed? "(CONT PROC)" ?
I originally found this studying the documentation of my current 1.8.7
release of guile and wondered, if its still present in the development
branch.
Bye -
Some Admiring Guile-User and Enlgisch Non-Native speaker:)
[-- Attachment #2: diff-c.txt --]
[-- Type: text/plain, Size: 975 bytes --]
*** api-control.texi.new 2010-09-03 23:09:44.671311883 +0200
--- guile-bf08e10/doc/ref/api-control.texi 2010-09-03 16:23:02.000000000 +0200
***************
*** 488,495 ****
@deffn {Scheme Procedure} call-with-current-continuation proc
@deffnx {Scheme Procedure} call/cc proc
@rnindex call-with-current-continuation
! Capture the current continuation and call @code{(@var{cont} @var{proc})}
! with it. The return value is the value returned by
@var{proc}, or when @code{(@var{cont} @var{value})} is later invoked,
the return is the @var{value} passed.
--- 488,495 ----
@deffn {Scheme Procedure} call-with-current-continuation proc
@deffnx {Scheme Procedure} call/cc proc
@rnindex call-with-current-continuation
! Capture the current continuation and call @code{(@var{proc}
! @var{cont})} with it. The return value is the value returned by
@var{proc}, or when @code{(@var{cont} @var{value})} is later invoked,
the return is the @var{value} passed.
next reply other threads:[~2010-09-03 21:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-03 21:47 ebuy [this message]
2010-09-04 17:02 ` typo/bug in guile-bf08e10/doc/ref/api-control.texi 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=1283550428.7803.20.camel@melody \
--to=rtfds@online.de \
--cc=bug-guile@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).