From: Mark H Weaver <mhw@netris.org>
To: Chris Marusich <cmmarusich@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Multiple values passed as single argument to procedure
Date: Sun, 11 Jun 2017 16:36:08 -0400 [thread overview]
Message-ID: <87k24i2rev.fsf@netris.org> (raw)
In-Reply-To: <87mv9fnejc.fsf@gmail.com> (Chris Marusich's message of "Sun, 11 Jun 2017 00:56:23 -0700")
Chris Marusich <cmmarusich@gmail.com> writes:
> I've noticed that when one passes multiple values as a single argument
> to a procedure, only the first value gets used. Is this expected?
Yes. Scheme has no concept of a "multiple values" object that can be
given a single name, or passed as a single argument to a procedure.
Returning multiple values from a procedure is analogous to passing
multiple arguments to a procedure.
Use 'call-with-values', 'let-values', or 'receive' to call a procedure
that returns multiple values (or no values).
If you do not use one of the above forms (or a macro that expands to one
of them) to call a procedure that returns multiple values, then Guile
will discard all but the first result. Note that this is a
Guile-specific extension. Other Scheme implementations may behave
differently (e.g. report an error) if multiple values (or no values) are
returned to a procedure call that was not done using one of the forms
listed above.
Mark
PS: I should mention that Guile does indeed have a "multiple values"
object at the C level only, to allow C code to return or accept
multiple values without uglifying the C calling convention for
Scheme procedures. This is to work around the fact that C does not
support returning multiple values from a function.
next prev parent reply other threads:[~2017-06-11 20:36 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 [this message]
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
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=87k24i2rev.fsf@netris.org \
--to=mhw@netris.org \
--cc=cmmarusich@gmail.com \
--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).