From: Kevin Ryde <user42@zip.com.au>
Cc: guile-devel@gnu.org
Subject: Re: list versus apply
Date: Mon, 06 Jun 2005 06:37:20 +1000 [thread overview]
Message-ID: <87hdgck0an.fsf@zip.com.au> (raw)
In-Reply-To: <87k6l8yam0.fsf@zagadka.de> (Marius Vollmer's message of "Sun, 05 Jun 2005 20:30:47 +0300")
Marius Vollmer <mvo@zagadka.de> writes:
>
> (define (list . args) args)
>
> is an acceptable definition of list. Is it not?
Yep, because args is of course a fresh list when calling a lambda, but
it looks like primitives (C code) aren't called with a copied list
like that.
(I guess having primitives like that makes some sense, only a few are
interested in modifying or re-using their input "rest" list.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-06-05 20:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-20 22:22 list versus apply Kevin Ryde
2005-04-22 23:45 ` Kevin Ryde
2005-06-05 17:30 ` Marius Vollmer
2005-06-05 20:37 ` Kevin Ryde [this message]
2005-06-05 21:11 ` Marius Vollmer
2005-06-05 21:21 ` Kevin Ryde
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=87hdgck0an.fsf@zip.com.au \
--to=user42@zip.com.au \
--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).