From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: Should we add scm_to_pointer, or just use SCM_POINTER_VALUE?
Date: Wed, 01 Feb 2012 11:59:19 +0100 [thread overview]
Message-ID: <87aa52sttk.fsf@pobox.com> (raw)
In-Reply-To: <87d39zdqhd.fsf@netris.org> (Mark H. Weaver's message of "Wed, 01 Feb 2012 01:20:30 -0500")
On Wed 01 Feb 2012 07:20, Mark H Weaver <mhw@netris.org> writes:
> Should we add 'scm_to_pointer'? For most other accessors, the trend
> seems to be to discourage use of C macros and move people over to C
> functions instead. With that in mind, it seems inconsistent to have
> people using SCM_POINTER_VALUE for lack of a C function to do this job.
>
> What do you think?
Sounds like a great idea to me.
Cheers,
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-02-01 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 6:20 Should we add scm_to_pointer, or just use SCM_POINTER_VALUE? Mark H Weaver
2012-02-01 10:59 ` Andy Wingo [this message]
2012-02-02 21:07 ` Ludovic Courtès
2012-02-02 21:49 ` Andy Wingo
2012-02-02 22:10 ` Mark H Weaver
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=87aa52sttk.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).