From: Edwin Young <edwiny@entropic.co.uk>
To: "'caml-list@inria.fr'" <caml-list@inria.fr>
Subject: 32 bit integers
Date: Mon, 18 Oct 1999 15:47:36 +0100 [thread overview]
Message-ID: <B1A05F46097FD211AD2300A0C9E6E8904E1B77@callisto.entropic.co.uk> (raw)
Hi,
several people have been requesting features to be included in a
forthcoming O'Caml/O'Labl merge, so I thought I'd add a humble plea for
some support for untagged (presumably boxed) integers. I'm looking
mostly at camlidl, the documentation for which says: "Since the Caml int
type has one bit of tag, the conversion from IDL types int and long
loses the most significant bit on 32-bit platforms". I don't think
that's terribly satisfactory. If there isn't going to be a 32-bit type,
can anyone suggest a workaround (eg can I convince camlidl to map all
ints to floats)?
Thanks,
--
Edwin Young
next reply other threads:[~1999-10-18 15:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-18 14:47 Edwin Young [this message]
1999-10-21 14:24 ` Xavier Leroy
1999-10-21 19:17 ` Scott Alexander
1999-10-22 0:00 ` John Prevost
1999-10-22 9:42 ` Xavier Leroy
1999-10-21 18:13 Manuel Fahndrich
1999-10-29 21:28 Juergen Pfitzenmaier
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=B1A05F46097FD211AD2300A0C9E6E8904E1B77@callisto.entropic.co.uk \
--to=edwiny@entropic.co.uk \
--cc=caml-list@inria.fr \
/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).