Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!husc6!ut-sally!nather
From: nather@ut-sally.UUCP
Newsgroups: comp.lang.c
Subject: Re: Distorting fseek semantics
Message-ID: <8993@ut-sally.UUCP>
Date: Sat, 12-Sep-87 14:59:25 EDT
Article-I.D.: ut-sally.8993
Posted: Sat Sep 12 14:59:25 1987
Date-Received: Sun, 13-Sep-87 08:25:37 EDT
References: <493@its63b.ed.ac.uk> <6061@brl-smoke.ARPA> <8560@utzoo.UUCP> <27734@sun.uucp>
Organization: U. Texas CS Dept., Austin, Texas
Lines: 16
Summary: MS-DOS fseek

In article <27734@sun.uucp>, guy@sun.uucp (Guy Harris) writes:
> 
> I have no idea how UNIX-like the "fseek" on MS-DOS C implementations really
> is.  

It's not so bad.  If the file is opened as a text file, it works just like
Unix, since the CR code is removed on input and restored on output.  If,
however, the file is opened in binary, then you must use ftell() to find
out where you are.


-- 
Ed Nather
Astronomy Dept, U of Texas @ Austin
{allegra,ihnp4}!{noao,ut-sally}!utastro!nather
nather@astro.AS.UTEXAS.EDU