caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Moore <jonm@dsl.cis.upenn.edu>
To: Michael Leary <leary@nwlink.com>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] flushing stdout with flush stdout not good?
Date: Mon, 03 Sep 2001 22:53:56 EDT	[thread overview]
Message-ID: <200109040253.f842ruW10866@codex.cis.upenn.edu> (raw)
In-Reply-To: Your message of "Mon, 03 Sep 2001 19:31:04 PDT." <20010903193104.A12284@ip178.usw22.rb1.bel.nwlink.com>

> if I write them this way:
> 
> let fso = flush stdout
> let name s = printf "Name %s\n" s; fso
> let color c = printf "Colour %s\n" c; fso

I think what you mean to write here is:

let fso () = flush stdout
let name s = printf "Name %s\n" s; fso ()
let color c = printf "Colour %s\n" c; fso ()

In the code you wrote above, "fso" gets bound to () (and not to a function)
after flushing stdout once. So the name and color functions you wrote are
doing prints, and returning units, rather than invoking the flush as you
thought. Thus, this is why the output becomes bursty (you're not actually
flushing).

Jon
..........
Jonathan Moore                              http://www.cis.upenn.edu/~jonm
University of Pennsylvania                          jonm@dsl.cis.upenn.edu
'Frater qui adiuvatur a fratre quasi civitas firma.' (Brother helped by
brother is a fortress).
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  parent reply	other threads:[~2001-09-04  2:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-03 19:27 Michael Leary
2001-09-03 20:02 ` Markus Mottl
2001-09-04  1:59   ` Michael Leary
2001-09-04  2:31     ` Michael Leary
2001-09-04  2:40       ` Alexander V. Voinov
2001-09-04  2:53       ` Jon Moore [this message]
2001-09-04 17:55         ` Michael Leary

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=200109040253.f842ruW10866@codex.cis.upenn.edu \
    --to=jonm@dsl.cis.upenn.edu \
    --cc=caml-list@inria.fr \
    --cc=leary@nwlink.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;
as well as URLs for NNTP newsgroup(s).