Article View: comp.sys.atari.st
Article #29220Re: FILE I/O
From: Preston Bannister
Date: Sat, 14 Nov 1987 21:53
Date: Sat, 14 Nov 1987 21:53
19 lines
1423 bytes
1423 bytes
>> There is a much simpler way to find the length of a file. You simply >> do an Fseek to the end of the file. This means of getting the length >> of a file is also usable with Unix and MSDOS (if not always necessary). >> (I'm doing this from memory): >This is a VERY slow way to do it. Especially on LARGE files where >the seek is worse than the open. The Fseek operation doesn't actually cause any physical disk activity. All the file system has to do implement Fseek is change it's internal 'position in file' number. (Assuming that the file system implementation isn't incredibly brain-damaged :-) -- Preston L. Bannister USENET : ucbvax!trwrb!felix!preston BIX : plb CompuServe : 71350,3505 GEnie : p.bannister
Technical Details
Message-ID:
<13005@felix.UUCP>Path:
arc1-ca.pugleaf.net!utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!sdcrdcf!trwrb!felix!prestonReferences:
<2023@homxc.UUCP> <183@decvax.UUCP> <12361@felix.UUCP> <800@xn.LL.MIT.EDU>Show Full Headers
Complete Article Headers
Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: arc1-ca.pugleaf.net!utzoo!mnetor!uunet!husc6!bloom-beacon!oberon!sdcrdcf!trwrb!felix!preston From: preston@felix.UUCP (Preston Bannister) Newsgroups: comp.sys.atari.st Subject: Re: FILE I/O Message-ID: <13005@felix.UUCP> Date: Sat, 14-Nov-87 16:53:41 EST Article-I.D.: felix.13005 Posted: Sat Nov 14 16:53:41 1987 Date-Received: Tue, 17-Nov-87 06:43:35 EST References: <2023@homxc.UUCP> <183@decvax.UUCP> <12361@felix.UUCP> <800@xn.LL.MIT.EDU> Sender: daemon@felix.UUCP Reply-To: preston@felix.UUCP (Preston Bannister) Organization: FileNet Corp., Costa Mesa, CA Lines: 19 Keywords: Mark Williams C, Fseek, fseek