From: Julien Moutinho <julien.moutinho@gmail.com>
To: Kaspar Rohrer <krohrer@student.ethz.ch>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Native multithreaded LablGTK2?
Date: Mon, 30 Jul 2007 13:57:25 +0200 [thread overview]
Message-ID: <20070730115725.GB28423@jiyu.gnu> (raw)
In-Reply-To: <93DE46B0-285F-4066-A1CA-0A3969C728B3@student.ethz.ch>
On Mon, Jul 30, 2007 at 10:01:47AM +0200, Kaspar Rohrer wrote:
>>> PS: Currently the application is single threaded, but due to output
>>> redirection using pipes, I get the occassional freeze. (Pipe gets flooded!)
>> Weird.
> No, not at all. The redirection happens in the same thread, so if the pipe
> buffer is full, all write operations will block. And because the
> application is single threaded, the reader never gets a chance to empty the
> pipe. Thus, freeze.
Oki douki, it's just that I did not undertand why you use std(in|out)
to communicate between threads... But you use them because you want
a buffering machinery and you have only looked at Pervasives, right?
> I'm piping stdout, because that's the only way I was able to redirect
> stdout to a gtk text widget (using a GIOchannel: GMain.Io.*). If anybody
> has a better idea, I'd be glad to hear it. I was originally thinking of an
> out_channel that writes to a buffer instead of a file, but the Ocaml
> standard library seems to be missing this functionality. Or is it?
You have [Stream.t], [Buffer.t] and [GText.buffer] at your service.
HTH.
next prev parent reply other threads:[~2007-07-30 11:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-29 19:16 Kaspar Rohrer
2007-07-30 5:40 ` [Caml-list] " Julien Moutinho
2007-07-30 8:01 ` Kaspar Rohrer
2007-07-30 11:57 ` Julien Moutinho [this message]
2007-07-30 13:22 ` Kaspar Rohrer
2007-07-30 8:22 ` Kaspar Rohrer
2007-07-30 10:01 ` Julien Moutinho
2007-07-30 11:31 ` Kaspar Rohrer
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=20070730115725.GB28423@jiyu.gnu \
--to=julien.moutinho@gmail.com \
--cc=caml-list@inria.fr \
--cc=krohrer@student.ethz.ch \
/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