From: Andy Wingo <INVALID.NOREPLY@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Andy Wingo" <wingo@pobox.com>,
bug-guile@gnu.org
Subject: [bug #31445] Incorrect multiple-value truncation [1.9.13]
Date: Fri, 19 Nov 2010 15:39:49 +0000 [thread overview]
Message-ID: <20101119-153949.sv20118.17846@savannah.gnu.org> (raw)
In-Reply-To: <20101118-213155.sv15145.46723@savannah.gnu.org>
Follow-up Comment #3, bug #31445 (project guile):
I could go either way. I think using a single-valued, truncating API is the
right thing to do though. Grep your tree for scm_call_ and scm_apply to see
the size of the set of current use cases.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?31445>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
prev parent reply other threads:[~2010-11-19 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-25 9:57 [bug #31445] Incorrect multiple-value truncation [1.9.13] Ludovic Courtès
2010-11-18 19:35 ` Andy Wingo
2010-11-18 21:31 ` Ludovic Courtès
2010-11-19 15:39 ` Andy Wingo [this message]
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=20101119-153949.sv20118.17846@savannah.gnu.org \
--to=invalid.noreply@gnu.org \
--cc=bug-guile@gnu.org \
--cc=ludo@gnu.org \
--cc=wingo@pobox.com \
/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).