From: Chris Hecker <checker@d6.com>
To: David Fox <dsfox@cogsci.ucsd.edu>, caml-list@inria.fr
Subject: Re: [Caml-list] in_channel_length fails for files longer than max_int
Date: Sat, 12 May 2001 23:24:32 -0700 [thread overview]
Message-ID: <4.3.2.7.2.20010512232232.00e65970@shell16.ba.best.com> (raw)
In-Reply-To: <luitj3swez.fsf@hci.ucsd.edu>
>The pervasive function in_channel_length fails when the file size is
>too large for an int, but it doesn't raise an exception. The code in
>io.c just checks for lseek errors. Would a check for end > max_int be
>worthwhile?
Shouldn't all of the file size stuff be converted to int64s now anyway?
Chris
-------------------
To unsubscribe, mail caml-list-request@inria.fr. Archives: http://caml.inria.fr
next prev parent reply other threads:[~2001-05-14 18:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <William Chesters's message of "Sun, 13 May 2001 23:29:24 +0200 (CEST)">
2001-05-14 16:55 ` David Fox
2001-05-13 6:24 ` Chris Hecker [this message]
2001-05-28 13:13 ` Xavier Leroy
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=4.3.2.7.2.20010512232232.00e65970@shell16.ba.best.com \
--to=checker@d6.com \
--cc=caml-list@inria.fr \
--cc=dsfox@cogsci.ucsd.edu \
/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).