From: Andreas Sommer <AndiDog@web.de>
To: David Allsopp <dra-news@metastack.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Calling OCaml from C - nothing shown on stdout
Date: Tue, 29 Jun 2010 14:45:31 +0200 [thread overview]
Message-ID: <4C29EAEB.6040203@web.de> (raw)
In-Reply-To: <E51C5B015DBD1348A1D85763337FB6D908F27E@Remus.metastack.local>
David Allsopp wrote:
>
>
> As far as I can tell from the manual, there's no particular difference in native code between using caml_main and caml_startup. Your problem is the buffering of stdout in the OCaml runtime. There are two ways of working around this:
>
The caml_main and caml_startup functions are indeed identical
(caml_startup only calls caml_main). You were right about the stdout
buffering, and I will use your flushed_printf solution. Thanks for your
help!
Andreas
prev parent reply other threads:[~2010-06-29 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-29 10:44 Andreas Sommer
2010-06-29 10:52 ` [Caml-list] " Erik de Castro Lopo
2010-06-29 11:18 ` David Allsopp
2010-06-29 11:52 ` Matthieu Dubuget
2010-06-29 12:45 ` Andreas Sommer [this message]
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=4C29EAEB.6040203@web.de \
--to=andidog@web.de \
--cc=caml-list@yquem.inria.fr \
--cc=dra-news@metastack.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