From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id EAA25975; Tue, 4 Sep 2001 04:31:32 +0200 (MET DST) X-Authentication-Warning: pauillac.inria.fr: majordomo set sender to owner-caml-list@pauillac.inria.fr using -f Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id EAA25898 for ; Tue, 4 Sep 2001 04:31:31 +0200 (MET DST) Received: from smtp.nwlink.com (smtp.nwlink.com [209.20.130.57]) by concorde.inria.fr (8.11.1/8.10.0) with ESMTP id f842VT115092 for ; Tue, 4 Sep 2001 04:31:30 +0200 (MET DST) Received: from ip178.usw22.rb1.bel.nwlink.com (ip178.usw22.rb1.bel.nwlink.com [207.202.195.178]) by smtp.nwlink.com (8.9.3/8.9.1) with SMTP id TAA18963 for ; Mon, 3 Sep 2001 19:29:38 -0700 (PDT) Received: (qmail 12369 invoked by uid 500); 4 Sep 2001 02:31:04 -0000 Date: Mon, 3 Sep 2001 19:31:04 -0700 From: Michael Leary To: Markus Mottl Cc: caml Subject: Re: [Caml-list] flushing stdout with flush stdout not good? Message-ID: <20010903193104.A12284@ip178.usw22.rb1.bel.nwlink.com> References: <20010903122740.A11704@ip178.usw22.rb1.bel.nwlink.com> <20010903220208.C8034@chopin.ai.univie.ac.at> <20010903185913.A12213@ip178.usw22.rb1.bel.nwlink.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010903185913.A12213@ip178.usw22.rb1.bel.nwlink.com>; from leary@nwlink.com on Mon, Sep 03, 2001 at 06:59:13PM -0700 Sender: owner-caml-list@pauillac.inria.fr Precedence: bulk I should give example: a series of about 13 functions like these: let name s = printf "Name %s" s; print_newline () let color c = printf "Colour %s" c; print_newline () about half have three or four arguments, usually floats 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 It becomes very ugly and "bursty". The only modules in use are Str, Printf, and List. -- ------------------- 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