From: David Kastrup <dak@gnu.org>
To: 11764@debbugs.gnu.org
Subject: bug#11764: Missing C API doc for accessing unknown number of values
Date: Fri, 22 Jun 2012 17:17:12 +0200 [thread overview]
Message-ID: <87pq8r74w7.fsf@fencepost.gnu.org> (raw)
<URL:http://www.gnu.org/software/guile/manual/html_node/Multiple-Values.html#Multiple-Values>
provides scm_c_value_ref for accessing a particular value from a values
object. There is no documented way for figuring out how many values
there are. There is no documented way for getting the complete list of
values in an object (Guile itself uses scm_struct_ref (value,SCM_INUM0)).
While there is a macro VALUESP for figuring out whether an SCM is a
values object, it is not documented either.
--
David Kastrup
next reply other threads:[~2012-06-22 15:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-22 15:17 David Kastrup [this message]
2012-07-04 15:52 ` bug#11764: Missing C API doc for accessing unknown number of values Andy Wingo
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=87pq8r74w7.fsf@fencepost.gnu.org \
--to=dak@gnu.org \
--cc=11764@debbugs.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).