From: Kevin Ryde <user42@zip.com.au>
Subject: doc gh scm_list_n and scm_apply_0
Date: Sat, 18 Oct 2003 11:50:28 +1000 [thread overview]
Message-ID: <87y8vj2u1n.fsf@zip.com.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 247 bytes --]
FYI,
* gh.texi (Calling Scheme procedures from C, scm transition summary):
Refer to scm_list_n, not the old name scm_listify.
(scm transition summary): For gh_apply, recommend scm_apply_0, which
is now documented.
[-- Attachment #2: gh.texi.listify.diff --]
[-- Type: text/plain, Size: 1297 bytes --]
--- gh.texi.~1.8.~ 2003-06-12 08:44:17.000000000 +1000
+++ gh.texi 2003-10-18 11:46:13.000000000 +1000
@@ -609,7 +609,7 @@
@deftypefunx SCM gh_list (SCM l0, SCM l1, ... , SCM_UNDEFINED)
These correspond to the Scheme @code{(cons a b)} and @code{(list l0 l1
...)} procedures. Note that @code{gh_list()} is a C macro that invokes
-@code{scm_listify()}.
+@code{scm_list_n()}.
@end deftypefun
@deftypefun SCM gh_car (SCM @var{obj})
@@ -1118,7 +1118,7 @@
Use @code{scm_set_car_x} and @code{scm_set_cdr_x} instead.
@item @code{gh_list}
-Use @code{scm_listify} instead.
+Use @code{scm_list_n} instead.
@item @code{gh_length}
Replace @code{gh_length (@var{lst})} by
@@ -1133,7 +1133,7 @@
@item @code{gh_append2}, @code{gh_append3}, @code{gh_append4}
Replace @code{gh_append@var{N} (@var{l1}, @dots{}, @var{lN})} by
@example
-scm_append (scm_listify (@var{l1}, @dots{}, @var{lN}, SCM_UNDEFINED))
+scm_append (scm_list_n (@var{l1}, @dots{}, @var{lN}, SCM_UNDEFINED))
@end example
@item @code{gh_reverse}
@@ -1161,7 +1161,6 @@
Use the @code{SCM_VECTOR_LENGTH} macro instead.
@item @code{gh_apply}
-Use @code{scm_apply} instead, but note that @code{scm_apply} takes an
-additional third argument that you should set to @code{SCM_EOL}.
+Use @code{scm_apply_0} instead.
@end table
[-- Attachment #3: Type: text/plain, Size: 142 bytes --]
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2003-10-18 1:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87y8vj2u1n.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).