Yeah, this seems surprising. In C I&#39;d often have fflush(stdout); In OCaml I make use of the %! printf feature. Normally I want output to be buffered, for efficiency, but I know points where I want to ensure a &quot;sync&quot; so that I&#39;m not looking at incomplete output. Mind you, I mostly use stdout/stderr for logging/printf traces...<div>
<br><div class="gmail_quote">On Sun, Jun 24, 2012 at 5:06 PM, Lukasz Stafiniak <span dir="ltr">&lt;<a href="mailto:lukstafi@gmail.com" target="_blank">lukstafi@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Mon, Jun 25, 2012 at 12:19 AM, Diego Olivier Fernandez Pons<br>
&lt;<a href="mailto:dofp.ocaml@gmail.com">dofp.ocaml@gmail.com</a>&gt; wrote:<br>
&gt;<br>
&gt; During all the years I have been coding, I had never had to worry<br>
&gt; about flushing I/O (when / why / how) in any language (C/C++, Java, C#<br>
&gt; and OCaml).<br>
&gt; I actually had even forgotten those things existed...<br>
<br>
</div>You haven&#39;t needed to flush output when debugging?<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Caml-list mailing list.  Subscription management and archives:<br>
<a href="https://sympa-roc.inria.fr/wws/info/caml-list" target="_blank">https://sympa-roc.inria.fr/wws/info/caml-list</a><br>
Beginner&#39;s list: <a href="http://groups.yahoo.com/group/ocaml_beginners" target="_blank">http://groups.yahoo.com/group/ocaml_beginners</a><br>
Bug reports: <a href="http://caml.inria.fr/bin/caml-bugs" target="_blank">http://caml.inria.fr/bin/caml-bugs</a><br>
<br>
</div></div></blockquote></div><br></div>