From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mail1-relais-roc.national.inria.fr (mail1-relais-roc.national.inria.fr [192.134.164.82])
	by walapai.inria.fr (8.13.6/8.13.6) with ESMTP id p929gOK9014825
	for <caml-list@sympa-roc.inria.fr>; Sun, 2 Oct 2011 11:42:24 +0200
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AlkDAB0xiE7UGyoBlGdsb2JhbABBhGWUfYxZgXIiAQEBAQkLCQkUAyKBUwEBBSMPAUURCxoCBRYLAgIJAwIBAgFFEwgBAYd5piSQKYEthGGBEwSTYIUljBs
X-IronPort-AV: E=Sophos;i="4.68,476,1312149600"; 
   d="scan'208";a="122455251"
Received: from smtp1-g21.free.fr ([212.27.42.1])
  by mail1-smtp-roc.national.inria.fr with ESMTP; 02 Oct 2011 11:42:18 +0200
Received: from [192.168.0.3] (bur91-2-82-231-161-160.fbx.proxad.net [82.231.161.160])
	(Authenticated sender: tiphaine.turpin)
	by smtp1-g21.free.fr (Postfix) with ESMTPA id 02DEB940248
	for <caml-list@inria.fr>; Sun,  2 Oct 2011 11:42:11 +0200 (CEST)
Message-ID: <4E884DEA.6080304@free.fr>
Date: Sun, 02 Oct 2011 13:41:30 +0200
From: Tiphaine Turpin <tiphaine.turpin@free.fr>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110427 Lightning/1.0b3pre Thunderbird/3.1.9
MIME-Version: 1.0
To: caml-list@inria.fr
References: <CAAmKFxeFBaqpbW8-rt3GOwvhNKaf2MjZdP20ZydpptksQcTVZA@mail.gmail.com>
In-Reply-To: <CAAmKFxeFBaqpbW8-rt3GOwvhNKaf2MjZdP20ZydpptksQcTVZA@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Subject: Re: [Caml-list] Problem with un-flushed output getting mangled

Le 30/09/2011 02:00, Taylor Venable a écrit :
> B. Although I link to Batteries (version 1.4.1) I don't use its IO
> layer.
If so, then my experience is probably irrelevant. But sometimes with
batteries there are "implicit" things. A long time ago I had a problem
which looked similar (output seemed interleaved some strange and very
sparse way). It turned out that the [open_in] function from batteries
was not using the right flags, in particular the "truncate" flag was not
set, so I was only overwriting the beginning of the file, which caused a
problem when a previous and longer version existed. This should have
been corrected now, but as batteries IO are a completely different
implementation, I would check the use of batteries with attention.

Tiphaine Turpin