From: Remi Vanicat <remi.vanicat@laposte.net>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Calling C from OCaml and data representation question
Date: Sat, 06 Mar 2004 04:18:40 +0100 [thread overview]
Message-ID: <87hdx2zmr3.dlv@vanicat.homelinux.org> (raw)
In-Reply-To: <20040306023818.58510.qmail@web41207.mail.yahoo.com> (Vasili Galchin's message of "Fri, 5 Mar 2004 18:38:18 -0800 (PST)")
Vasili Galchin <vasiliocaml@yahoo.com> writes:
> Hello,
>
> I am working on some run-time library project. I
> have read in the online "OReilly" book the chapter
> where it discusses data representation in particular C
> functions, Long_val and Int_val. Is there really the
> preferred way to handle data representation issues
> from OCaml to C?? The reason I ask is that C is really
> very bad about types like "int" and "long", i.e. these
> types are not portable. It is really better to use
> "unit32", "unit64", etc. If I have a 32 bit entity,
> how can I use Long_val and Int_val safely?
the ocaml specification tell us that an int on a 32 bit platform is
an integer on 31 bit, an int on a 64 bit platform is an integer on 63
bit, and so one. So beware. If you have really a 32 bit entity, may be
you should use the int32 type. There is the "copy_int32" function in
alloc.h and the Int32_val define in mlvalues.h for manipulating them.
--
Rémi Vanicat
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2004-03-06 3:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-06 2:38 Vasili Galchin
2004-03-06 3:18 ` Remi Vanicat [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87hdx2zmr3.dlv@vanicat.homelinux.org \
--to=remi.vanicat@laposte.net \
--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