caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Nathaniel J. Gaylinn" <ngaylinn@cs.brown.edu>
To: caml-list@yquem.inria.fr
Subject: OCaml IDE (OCaml and stdout/stderr)
Date: Mon, 20 Jun 2005 16:08:29 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.58.0506201608110.2193@point> (raw)


My program is having a hard time coping with how OCaml splits its output
between stdout and stderr. The order in which a line of output is received
from OCaml's stdout and a warning from its stderr seems to be completely
random and therefore my program's output is also random. I'm pretty sure
this has to do with how OCaml buffers stdout, but I'm not sure how to
change this.

To make my program more portable, I'm writing it using the QT toolkit
which has a nice abstraction of inter-process communication in a class
called QProcess. This is what I'm using to communicate with OCaml.

>From your experience, do you think the buffering is taking place on
OCaml's end or on Qt's? Some research seems to suggest that how output is
buffered from a program can be controlled from within that program (since
there is direct access to the various output streams) but not from
outside. If that's true, then the buffering problem must be inside OCaml.

Is there any nice way to force OCaml to flush its output buffers more
often? Is there any way to customize what data OCaml sends to stdout and
what it sends to stderr (this would be a nice feature to have!)? Do any
other ideas come to mind?

Thanks,

  -- Nate Gaylinn


             reply	other threads:[~2005-06-20 20:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-20 20:08 Nathaniel J. Gaylinn [this message]
2005-06-21  0:34 ` [Caml-list] " Jacques Garrigue
2005-06-21 13:33   ` Nathaniel J. Gaylinn
2005-06-21 14:13     ` Nathaniel J. Gaylinn
2005-06-21  1:13 ` Brian Hurt

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=Pine.LNX.4.58.0506201608110.2193@point \
    --to=ngaylinn@cs.brown.edu \
    --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).