From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id RAA03871; Fri, 15 Oct 2004 17:04:19 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id RAA03859 for ; Fri, 15 Oct 2004 17:04:18 +0200 (MET DST) Received: from kaiserslautern1.lms-gmbh.de (kaiserslautern1.lms-gmbh.de [212.43.68.201]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id i9FF4HMG010005 for ; Fri, 15 Oct 2004 17:04:18 +0200 Received: by kaiserslautern1.lms-gmbh.de with Internet Mail Service (5.5.2653.19) id ; Fri, 15 Oct 2004 17:04:17 +0200 Message-ID: From: "Bauer, Christoph" To: caml-list@inria.fr Subject: AW: [Caml-list] OCaml-3.08.1/MinGW: alloc_tuple fails Date: Fri, 15 Oct 2004 17:04:16 +0200 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4B2C8.3D8869D0" X-Miltered: at concorde with ID 416FE6F1.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Loop: caml-list@inria.fr X-Spam: no; 0.00; bauer:01 bauer:01 caml-list:01 mingw:01 alloc:01 andrieu:01 alloc:01 initialise:01 gcc:01 damien:01 bug:01 faq:01 faq:01 beginner's:01 beginners:01 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C4B2C8.3D8869D0 Content-Type: text/plain > On Oct 15, 2004, at 15:45, Olivier Andrieu wrote: > > > Hum, doesn't alloc_tuple(n) (which is simply alloc(n, 0)) already > > initialise the block with zeroes ? > > Oops, that's true, so it's OK to use Store_field. > > I have another theory for Christoph's problem: maybe some > incompatibility between C and C++ calling conventions. Is it > supposed to work when you compile a C file with a C++ > compiler, then link it with other C files compiled with a C compiler? I tried both versions, the first one compiled and linked with gcc, the second with g++. No success. caml_tuple isn't used very often in the base library. > > -- Damien > > ------------------- > 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 ------_=_NextPart_001_01C4B2C8.3D8869D0 Content-Type: text/html Content-Transfer-Encoding: quoted-printable AW: [Caml-list] OCaml-3.08.1/MinGW: alloc_tuple fails

> On Oct 15, 2004, at 15:45, Olivier Andrieu = wrote:
>
> > Hum, doesn't alloc_tuple(n) (which is = simply alloc(n, 0)) already
> > initialise the block with zeroes ?
>
> Oops, that's true, so it's OK to use = Store_field.
>
> I have another theory for Christoph's problem: = maybe some
> incompatibility between C and C++ calling = conventions.  Is it
> supposed to work when you compile a C file with = a C++
> compiler, then link it with other C files = compiled with a C compiler?

I tried both versions, the first one compiled and = linked with gcc, the
second with g++. No success.

caml_tuple isn't used very often in the base = library.



>
> -- Damien
>
> -------------------
> 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

------_=_NextPart_001_01C4B2C8.3D8869D0-- ------------------- 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