From: Kevin Ryde <user42@zip.com.au>
Subject: doc subr rest arg
Date: Thu, 21 Apr 2005 08:25:27 +1000 [thread overview]
Message-ID: <8764yhgk6g.fsf@zip.com.au> (raw)
I added a bit to scm_c_define_gsubr about not changing the rest arg.
Existing:
If RST is non-zero, then any arguments after the first `REQ + OPT'
are packaged up as a list and passed as FUNCTION's last argument.
Add:
FUNCTION must not modify that list. (Because when subr is called
through `apply' the list comes directly from the `apply' list
argument. This list is copied when dispatching to a scheme
procedure, but not when going to a subr.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
reply other threads:[~2005-04-20 22:25 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=8764yhgk6g.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).