From: ludo@gnu.org (Ludovic Courtès)
To: guile-user@gnu.org
Cc: guile-devel@gnu.org
Subject: Re: are double cells safe to use?
Date: Tue, 29 Oct 2013 13:22:15 +0100 [thread overview]
Message-ID: <871u34s1vs.fsf@gnu.org> (raw)
In-Reply-To: CA+Sr8wVQcU-tBSr1E3u5pgaS530_YCY3Ea4gH4HwXMoSUS1rWQ@mail.gmail.com
Hi,
Roland Orre <roland.orre@gmail.com> skribis:
> Sorry, double cells are even encouraged to use according the manual under
> "Allocating cells" (I had missed that)
> and no specific cares as long as they contain only SCM.
Well, that part of the manual is slightly deprecated. ;-)
I’d recommend using an appropriate data type instead. If the code you
write is in Scheme, you’d better use records (info "(guile) Record
Overview").
If the code is in C, you’d better use ‘scm_gc_malloc’ and allocate as
much room as needed to hold your C struct.
HTH!
Ludo’.
next prev parent reply other threads:[~2013-10-29 12:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 10:15 are double cells safe to use? Roland Orre
2013-10-29 10:45 ` Roland Orre
2013-10-29 12:22 ` Ludovic Courtès [this message]
2013-10-29 17:17 ` Mark H Weaver
2013-10-29 18:04 ` Roland Orre
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=871u34s1vs.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).