delorie.com/archives/browse.cgi | search |
From: | Martin Stromberg <eplmst AT epl DOT ericsson DOT se> |
Message-Id: | <200206021336.PAA14951@lws256.lu.erisoft.se> |
Subject: | Re: open(), fopen() don't check for llseek() failure |
To: | djgpp-workers AT delorie DOT com |
Date: | Sun, 2 Jun 2002 15:36:48 +0200 (MET DST) |
In-Reply-To: | <Pine.SUN.3.91.1020602155924.14325B@is> from "Eli Zaretskii" at Jun 02, 2002 03:59:56 PM |
X-Mailer: | ELM [version 2.5 PL3] |
MIME-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
Eli said: > On Sun, 2 Jun 2002, Richard Dawe wrote: > > When open and fopen are called to open & append to a file, they don't check > > that llseek() is successful. I think they should fail, if the seek was > > unsuccessful. Should this be fixed? > > When do we expect llseek to fail? Never, except perhaps for devices. Nevertheless, perhaps we should be prepared if it does fail although it never should? Right, MartinS
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |