From: Matthieu Dubuget <matthieu.dubuget@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] int overflow and Marshal failure
Date: Fri, 31 Aug 2007 20:25:24 +0200 [thread overview]
Message-ID: <46D85D14.3070109@gmail.com> (raw)
In-Reply-To: <1188577819.7084.21.camel@MATHIAS-ENS>
Mathias Kende a écrit :
> Le jeudi 30 août 2007 à 23:47 +0200, Markus E L a écrit :
>
>> A check in the Unix library would be nice, in the long run I think
>> using 32bit native integers is absolutely required.
>>
>
> I had the same sort of problem with the Unix.stat function and the
> st_size member being an int while it is a 64 bits int on recent systems
> (including some 32 bits one). The maximum size that can be stored on 32
> bits system, 1Go, is much too small for this function.
>
I think that the Largefile sub-module solves this problem.
Salutations
prev parent reply other threads:[~2007-08-31 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-30 21:47 Unix.getuid() int overflow Markus E L
2007-08-30 22:57 ` [Caml-list] " Markus E L
2007-08-31 16:30 ` [Caml-list] int overflow and Marshal failure Mathias Kende
2007-08-31 16:47 ` Eric Cooper
2007-08-31 16:49 ` Vincent Hanquez
2007-08-31 17:03 ` Brian Hurt
2007-08-31 18:25 ` Matthieu Dubuget [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=46D85D14.3070109@gmail.com \
--to=matthieu.dubuget@gmail.com \
--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