On Sam, 2004-10-16 at 19:51, Yamagata Yoriyuki wrote:
> From: David MENTRE <dmentre@linux-france.org>
> Subject: Re: [Caml-list] Flush behavior of baseic I/O class type
> Date: Sat, 16 Oct 2004 18:26:24 +0200
> 
> > Yamagata Yoriyuki <yoriyuki@mbg.ocn.ne.jp> writes:
> > 
> > >   1) Output as far as possible, and leave the rest.
> > >   2) raise an exception
> > >   3) undefined.
> > 
> > Or  4) call blocked until the whole buffer can be flushed.
> 
> It may be ok for non-blocking I/O, but it will cause "busy-waiting" ,
> so perhaps a user does not like it.  Moreover, for example, if the
> channel is actually a filter, and it needs more inputs to determine
> the next output, then it will stuck forever.  (See the case of the
> multibyte charcter code converter in the previous mail)
> 
> The easiest way (from the implementer's point of the view) would be
> 1), or 1') do the best effort to output, but nothing is guaranteed.
> However I'm afraid that it will cause a subtle I/O bug.

Which one?

We need "flush" to ensure data is actually communicated to the other
endpoint of the channel, i.e. it is a means of synchronisation. When the
data are sent in a way this synchronisation cannot be done, this feature
is used in the wrong way, and I think raising an exception would be
justified.

Well, this is why we _need_ "flush" sometimes. There may be other
situations where softer requirements suffice, e.g. when "flush" is
called for debugging purposes such that as much as data as possible are
printed.

So I think there is no general rule, it depends on the purpose "flush"
is used for.

Gerd
-- 
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany 
gerd@gerd-stolpmann.de          http://www.gerd-stolpmann.de
------------------------------------------------------------

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners