From: ludo@gnu.org (Ludovic Courtès)
To: Andy Wingo <wingo@pobox.com>
Cc: "Mark H. Weaver" <mhw@netris.org>, guile-devel@gnu.org
Subject: Re: scm_to_pointer vs scm->pointer
Date: Thu, 05 Jul 2012 18:11:51 +0200 [thread overview]
Message-ID: <87a9ze2nnc.fsf@gnu.org> (raw)
In-Reply-To: <87k3yja6ae.fsf@pobox.com> (Andy Wingo's message of "Wed, 04 Jul 2012 17:35:05 +0200")
Hi,
Andy Wingo <wingo@pobox.com> skribis:
> On Tue 03 Jul 2012 23:47, ludo@gnu.org (Ludovic Courtès) writes:
>
>>> This should be fixed. Otherwise it's impossible to document in any
>>> sane fashion.
>>>
>>> Suggestion: change scm_to_pointer to SCM_POINTER_VALUE. WDYT?
>>
>> I’m happy with this change. Mark?
>>
>> (Back then, I was skeptical about the usefulness of the C pointer API.
>> I have since used ‘SCM_POINTER_VALUE’ and ‘scm_from_pointer’ in
>> Guile-GCC, which uses a mixed dynamic/static FFI, and for good reasons.)
>
> On second thought, let's leave it in. It is terribly confusing, but
> alternatives are worse.
We could also document ‘SCM_POINTER_VALUE’, WDYT?
Ludo’.
prev parent reply other threads:[~2012-07-05 16:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 21:38 scm_to_pointer vs scm->pointer Andy Wingo
2012-07-03 21:47 ` Ludovic Courtès
2012-07-04 15:35 ` Andy Wingo
2012-07-05 16:11 ` Ludovic Courtès [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=87a9ze2nnc.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).