From: Doug Evans <xdje42@gmail.com>
To: guile-devel <guile-devel@gnu.org>
Subject: guile struct members are not a good 1-1 match for c structs
Date: Tue, 29 Apr 2014 18:51:46 -0700 [thread overview]
Message-ID: <CAP9bCMQs3SfaNBHyP1aeV7cE-CJjoa4PPK5KPfHw=vYJYT1izA@mail.gmail.com> (raw)
Hi all.
While reading guile sources I happened across the implementation
of struct scm_print_state. ref: libguile/print.h
It (tries to) map a C struct to a set of Guile struct fields:
ref: SCM_PRINT_STATE_LAYOUT.
I *could* be missing something, but I think my angst can be represented
with the following question:
Has anyone tried to use scm_print_state from Scheme as a Guile struct
on a host with 64 bit words and 32 bit ints and 32 bit longs?
[P.S. This is with guile 2.0.9., which is what I have on my laptop -
currently travelling and don't currently have access to the git tree.]
next reply other threads:[~2014-04-30 1:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-30 1:51 Doug Evans [this message]
2014-04-30 7:24 ` guile struct members are not a good 1-1 match for c structs Andy Wingo
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='CAP9bCMQs3SfaNBHyP1aeV7cE-CJjoa4PPK5KPfHw=vYJYT1izA@mail.gmail.com' \
--to=xdje42@gmail.com \
--cc=guile-devel@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).