unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Julian Graham <joolean@gmail.com>
Cc: Guile Users <guile-user@gnu.org>
Subject: Re: Accessing multiple values from C
Date: Mon, 09 Jan 2012 19:54:35 +0100	[thread overview]
Message-ID: <87r4z86710.fsf@pobox.com> (raw)
In-Reply-To: <CANdC_RDgPAB_=Cq88-ecGJz4W-YJTUUJFhpXJ6Zs7p2nQzrcYQ@mail.gmail.com> (Julian Graham's message of "Tue, 1 Nov 2011 11:34:08 -0400")

Hi,

On Tue 01 Nov 2011 16:34, Julian Graham <joolean@gmail.com> writes:

> I was playing around with some C code that uses the new R6RS
> bytevector ports, and I noticed that there doesn't seem to be an easy
> way (a la `let-values' or `receive') to access multiple return values
> from C.  I've resorted to doing:
>
>   scm_struct_ref (foo, SCM_INUM0);
>
> ...which is almost certainly not future-proof.  All I want to do is
> access these values as a pair or list.  Is there a Right Way to do
> that?

Not yet.  You interested in adding scm_c_value_ref (SCM, size_t) to the
API, and documentation to api-control.texi?  If you do it soon, it
will make it into 2.0.4.

Andy
-- 
http://wingolog.org/



  parent reply	other threads:[~2012-01-09 18:54 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 15:34 Accessing multiple values from C Julian Graham
2011-11-01 22:57 ` Ludovic Courtès
2012-01-09 18:54 ` Andy Wingo [this message]
2012-01-09 19:00   ` Julian Graham
2012-01-12  4:50     ` Julian Graham
2012-01-15 21:47       ` Ludovic Courtès
2012-01-16  9:05         ` Andy Wingo
2012-01-18  3:15       ` Mark H Weaver
2012-01-18 16:20         ` Andy Wingo
2012-01-18 20:19         ` Ludovic Courtès
2012-01-18 21:01           ` Mark H Weaver
2012-01-18 21:44             ` Ludovic Courtès
2012-01-18 21:47             ` Mark H Weaver
2012-01-18 23:06               ` Mark H Weaver
2012-01-18 21:01           ` Julian Graham

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=87r4z86710.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-user@gnu.org \
    --cc=joolean@gmail.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).