From: Richard Jones <rich@annexia.org>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Int32 and boxing
Date: Mon, 13 Aug 2007 18:55:01 +0100 [thread overview]
Message-ID: <20070813175501.GA24394@furbychan.cocan.org> (raw)
In-Reply-To: <200708130508.10023.jon@ffconsultancy.com>
On Mon, Aug 13, 2007 at 05:08:09AM +0100, Jon Harrop wrote:
>
> Are int32s are boxed on a 64-bit machine?
Unfortunately yes:
# Obj.is_block (Obj.repr 1_l);;
- : bool = true
# Sys.word_size;;
- : int = 64
I deal a lot with int32 and int64 types when interfacing with other
languages, so this causes an annoyance. I'm not sure what the
implications would be of having a different representation on 32 and
64 bit machines. I guess Marshal would have to go through hoops for a
start.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2007-08-13 17:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-13 4:08 Jon Harrop
2007-08-13 17:55 ` Richard Jones [this message]
2007-08-15 6:48 ` [Caml-list] " Jon Harrop
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20070813175501.GA24394@furbychan.cocan.org \
--to=rich@annexia.org \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.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 NNTP newsgroup(s).