From: Anthony Tavener <anthony.tavener@gmail.com>
To: Lukasz Stafiniak <lukstafi@gmail.com>
Cc: Diego Olivier Fernandez Pons <dofp.ocaml@gmail.com>,
OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] print_int is too slow
Date: Sun, 24 Jun 2012 17:52:39 -0600 [thread overview]
Message-ID: <CAN=ouMTHDLWUKR5PFA34Doo_UUtUEXyTmEZBTao=UGJfRdJqpA@mail.gmail.com> (raw)
In-Reply-To: <CAJMfKEWeOWTKgFvB4KDyzXaGs94L9ppcvA7WQqyDSdBEOQ0bVA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Yeah, this seems surprising. In C I'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 "sync" so that
I'm not looking at incomplete output. Mind you, I mostly use stdout/stderr
for logging/printf traces...
On Sun, Jun 24, 2012 at 5:06 PM, Lukasz Stafiniak <lukstafi@gmail.com>wrote:
> On Mon, Jun 25, 2012 at 12:19 AM, Diego Olivier Fernandez Pons
> <dofp.ocaml@gmail.com> wrote:
> >
> > During all the years I have been coding, I had never had to worry
> > about flushing I/O (when / why / how) in any language (C/C++, Java, C#
> > and OCaml).
> > I actually had even forgotten those things existed...
>
> You haven't needed to flush output when debugging?
>
> --
> Caml-list mailing list. Subscription management and archives:
> https://sympa-roc.inria.fr/wws/info/caml-list
> Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
> Bug reports: http://caml.inria.fr/bin/caml-bugs
>
>
[-- Attachment #2: Type: text/html, Size: 1703 bytes --]
next prev parent reply other threads:[~2012-06-24 23:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-24 18:40 Diego Olivier Fernandez Pons
2012-06-24 18:59 ` Gabriel Scherer
2012-06-24 19:08 ` Diego Olivier Fernandez Pons
2012-06-24 19:18 ` Oliver Bandel
2012-06-24 19:26 ` Diego Olivier Fernandez Pons
2012-06-24 19:48 ` Adrien
[not found] ` <20120624.220220.2022399462583597382.Christophe.Troestler@umons.ac.be>
2012-06-24 22:19 ` Diego Olivier Fernandez Pons
2012-06-24 23:06 ` Lukasz Stafiniak
2012-06-24 23:52 ` Anthony Tavener [this message]
2012-06-25 0:09 ` Diego Olivier Fernandez Pons
2012-06-25 11:39 ` oliver
2012-06-25 13:04 ` Gabriel Scherer
2012-06-25 14:25 ` oliver
2012-06-25 17:31 ` Florian Weimer
2012-06-25 10:07 ` Goswin von Brederlow
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='CAN=ouMTHDLWUKR5PFA34Doo_UUtUEXyTmEZBTao=UGJfRdJqpA@mail.gmail.com' \
--to=anthony.tavener@gmail.com \
--cc=caml-list@inria.fr \
--cc=dofp.ocaml@gmail.com \
--cc=lukstafi@gmail.com \
/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