From: Mark H Weaver <mhw@netris.org>
To: David Kastrup <dak@gnu.org>
Cc: guile-user@gnu.org
Subject: Re: Multiple values passed as single argument to procedure
Date: Mon, 12 Jun 2017 07:31:34 -0400 [thread overview]
Message-ID: <87wp8h1lyh.fsf@netris.org> (raw)
In-Reply-To: <87mv9d7dfu.fsf@fencepost.gnu.org> (David Kastrup's message of "Mon, 12 Jun 2017 11:39:01 +0200")
I'm sorry David, but _everything_ that you wrote below is incorrect.
David Kastrup <dak@gnu.org> writes:
> Chris Marusich <cmmarusich@gmail.com> writes:
>
>> I think I'm missing something here. In (list (f)), the call to f
>> certainly looks like it's happening at a position that one might
>> intuitively call a "tail" position.
>
> It is,
No it isn't.
> but list does not take multiple values
Yes it does. 'list' accepts an arbitrary number of values (arguments).
> and thus discards additional values returned by f.
'list' does not discard anything. The additional values are discarded
before 'list' is called.
> If list were a procedure/continuation accepting multiple values,
See above.
> would likely work as you expected.
It would not work as Chris expected no matter what procedure was called.
I will try to clarify all of this in another message.
Mark
next prev parent reply other threads:[~2017-06-12 11:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-11 7:56 Multiple values passed as single argument to procedure Chris Marusich
2017-06-11 8:28 ` David Kastrup
2017-06-11 20:36 ` Mark H Weaver
2017-06-11 21:31 ` Mark H Weaver
2017-06-12 0:19 ` Chris Marusich
2017-06-12 4:25 ` Mark H Weaver
2017-06-12 8:19 ` Chris Marusich
2017-06-12 8:55 ` Neil Jerram
2017-06-12 9:48 ` Neil Jerram
2017-06-12 9:39 ` David Kastrup
2017-06-12 11:31 ` Mark H Weaver [this message]
2017-06-12 14:24 ` David Kastrup
2017-06-13 2:26 ` Mark H Weaver
2017-06-13 3:09 ` Mark H Weaver
2017-06-13 3:45 ` Mark H Weaver
2017-06-13 11:17 ` dsmich
2017-06-26 11:25 ` Alex Vong
-- strict thread matches above, loose matches on Subject: below --
2017-09-01 19:39 Chris Marusich
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=87wp8h1lyh.fsf@netris.org \
--to=mhw@netris.org \
--cc=dak@gnu.org \
--cc=guile-user@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).