From: Alessandro Baretta <alex@baretta.com>
To: malc <malc@pulsesoft.com>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] (Sorry for my last post) lazyness, exceptions?, ocaml syntax rule-of-thumbs
Date: Mon, 30 Sep 2002 03:19:17 +0200 [thread overview]
Message-ID: <3D97A695.2090002@baretta.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0209300427310.1961-100000@home.oyster.ru>
malc wrote:
> On Sun, 29 Sep 2002, Alessandro Baretta wrote:
>
>
>>malc wrote:
>>
>>>I might be way off here, but shouldnt it be:
>>>
>>>let input_file_as_string file =
>>> let chanin = open_in_bin file in
>>> let len = in_channel_length chanin in
>>> let s = String.create len in
>>> really_input chanin s 0 (pred len);
>>> close_in chanin;
>>> s
>>
>># in_channel_length stdin;;
>>Exception: Sys_error "Illegal seek".
>
>
> Yes, but the function should be called: input_channel[stream]_as_string,
> no?
>
Scratch... Scratch... I'm not sure what you mean.
My point is just that in_channel_length is only meaningful
for channels connected to regular files. Otherwise, it
raises Sys_error. Maxence Guesdon's version handles this
case correctly, since it assumes that a channel is at the
EOF if-and-only-if reading from it raises End_of_file.
If you mean that the name of function seems to imply that
its parameter is a regular file, I disagree with you. In
UNIX anything you can do IO onto is a _file_ descriptor. In
C buffered IO is done through FILE* variables. One simply
has to write code which correctly handles the different
kinds of files that exist in the UNIX world. Some you can
seek on; on others you cannot, and all you can do is
continue to read until there is nothing left to read -- that
is fread(fdesc, buf, max) returns 0 when max > 0.
Alex
-------------------
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
next parent reply other threads:[~2002-09-30 1:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.44.0209300427310.1961-100000@home.oyster.ru>
2002-09-30 1:19 ` Alessandro Baretta [this message]
2002-09-26 15:50 Kontra, Gergely
2002-09-27 8:01 ` Maxence Guesdon
2002-09-27 8:14 ` Xavier Leroy
2002-09-27 10:29 ` Kontra, Gergely
2002-09-27 14:50 ` Florian Hars
2002-09-27 15:07 ` Maxence Guesdon
2002-09-27 17:06 ` Kontra, Gergely
2002-09-27 18:22 ` Tim Freeman
2002-09-27 22:27 ` malc
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=3D97A695.2090002@baretta.com \
--to=alex@baretta.com \
--cc=caml-list@inria.fr \
--cc=malc@pulsesoft.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