From: Damien Doligez <damien.doligez@inria.fr>
To: OCaml mailing list <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] OCaml + mingw-w64
Date: Mon, 22 Nov 2010 16:33:08 +0100 [thread overview]
Message-ID: <BE4C3D34-117E-4BFF-BBE7-C569FA0C8DF0@inria.fr> (raw)
In-Reply-To: <2017975850.988226.1290427453930.JavaMail.root@zmbs1.inria.fr>
On 2010-11-22, at 13:04, Christoph Cullmann wrote:
> In ocaml 3.12, in byterun/major_gc.h, there is:
>
> intnat caml_major_collection_slice (long howmuch)
>
> whereas in the .c file that is:
>
> intnat caml_major_collection_slice (intnat howmuch)
>
> As intnat is with mingw-w64 long long, this doesn't match.
> Should not the header use intnat, too?
You're right. This will be fixed in 3.12.1.
-- Damien
next parent reply other threads:[~2010-11-22 15:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2017975850.988226.1290427453930.JavaMail.root@zmbs1.inria.fr>
2010-11-22 15:33 ` Damien Doligez [this message]
2010-11-23 16:31 ` Christoph Cullmann
2010-11-24 7:14 ` Christoph Cullmann
2010-11-24 8:16 Christoph Cullmann
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=BE4C3D34-117E-4BFF-BBE7-C569FA0C8DF0@inria.fr \
--to=damien.doligez@inria.fr \
--cc=caml-list@yquem.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).