caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: skaller <skaller@users.sourceforge.net>
To: Nuutti Kotivuori <naked+caml@naked.iki.fi>
Cc: skaller@users.sourceforge.net, caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Bug with really_input under cygwin
Date: 12 Mar 2004 02:21:14 +1100	[thread overview]
Message-ID: <1079018473.2452.174.camel@pelican.wigram> (raw)
In-Reply-To: <87znao0ydf.fsf@aka.i.naked.iki.fi>

On Thu, 2004-03-11 at 16:02, Nuutti Kotivuori wrote:
> skaller@users.sourceforge.net wrote:

> But - there's nothing ambiguous about slurping an entire file into a
> string. And there's nothing complex about doing that portably.

A file is an abstraction, meaning it is a collection of 
access methods. There's no 'bytes' in a file, the bytes 
are just values return from the read function or submitted 
to the write function.

Many files exist with many different access methods.
Even the same physical disk data can be different
file abstractions: eg Unix directory.

The data on an unbuffered non-blocking serial communication 
link cannot be read with the block reading algorithm I gave:
end of data occurs before end of file -- if there is an end
of file .. eg it won't work on a raw terminal.

Yes, I know we have strayed a long way from the original
question, but I think the issue here is: the manual
isn't precise enough, but making it so is in fact very
difficult, so the Ocaml team is 'forgiven'. That's what
I think I was trying to say :D

-- 
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850, 
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net



-------------------
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


  reply	other threads:[~2004-03-11 15:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-09 22:30 Eric Dahlman
2004-03-09 22:52 ` Karl Zilles
2004-03-10  3:06 ` skaller
2004-03-10  4:10   ` David Brown
2004-03-10 13:14     ` Richard Zidlicky
2004-03-11  4:11       ` skaller
2004-03-11  3:24     ` skaller
2004-03-10 15:25   ` Nuutti Kotivuori
2004-03-11  3:42     ` skaller
2004-03-11  5:02       ` Nuutti Kotivuori
2004-03-11 15:21         ` skaller [this message]
2004-03-11  6:32       ` james woodyatt

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=1079018473.2452.174.camel@pelican.wigram \
    --to=skaller@users.sourceforge.net \
    --cc=caml-list@pauillac.inria.fr \
    --cc=naked+caml@naked.iki.fi \
    /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).