From: Andy Wingo <wingo@pobox.com>
To: Alexei Matveev <alexei.matveev@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Guile API for foreign languages: proposing SCM scm_list_0(void)
Date: Thu, 31 Jan 2013 18:23:52 +0100 [thread overview]
Message-ID: <87r4l1qn9z.fsf@pobox.com> (raw)
In-Reply-To: <CACMrLActZjmLTHX-HYCWsPjXqytv+5URaJmdJof5mjyJk3T7kg@mail.gmail.com> (Alexei Matveev's message of "Thu, 31 Jan 2013 17:57:21 +0100")
On Thu 31 Jan 2013 17:57, Alexei Matveev <alexei.matveev@gmail.com> writes:
>> static const scm_t_bits my_false = 0x4;
>> static const scm_t_bits my_true = 0x404;
>> static const scm_t_bits my_nil = 0x104;
>> static const scm_t_bits my_eof = 0xa04;
>> static const scm_t_bits my_eol = 0x304;
>> static const scm_t_bits my_unspecified = 0x804;
>
> I get slightly different values for 1.8 (32 bit x86)
Yes, it is possible to have different values for these. They are part
of the ABI, not the API. As such, the values of these constants are the
same throughout one stable release series. So they have one set of
values for 1.8, another for 2.0, another for 2.2, etc.
In theory they are architecture-dependent but in practice they are the
same on all architectures, 32-bit or 64-bit, ARM or x86, etc.
> I used this slightly modified code to get those numbers:
Go ahead and generate Fortran code, I would say :) No sense in
bothering to generate C.
Cheers,
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2013-01-31 17:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-02 11:11 Guile API for foreign languages: proposing SCM scm_list_0(void) Alexei Matveev
2013-01-12 15:16 ` Andy Wingo
2013-01-14 22:44 ` Alexei Matveev
2013-01-15 9:06 ` Andy Wingo
2013-01-15 9:20 ` Ludovic Courtès
2013-01-22 10:55 ` Andy Wingo
2013-01-31 11:27 ` Andy Wingo
2013-01-31 11:45 ` Andy Wingo
2013-01-31 13:37 ` Noah Lavine
2013-01-31 14:13 ` Alexei Matveev
2013-01-31 16:57 ` Alexei Matveev
2013-01-31 17:23 ` Andy Wingo [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=87r4l1qn9z.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=alexei.matveev@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).