Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!bbn!rochester!stuart
From: stuart@cs.rochester.edu (Stuart Friedberg)
Newsgroups: comp.sys.atari.st
Subject: Re: FILE I/O
Message-ID: <4039@sol.ARPA>
Date: Mon, 9-Nov-87 06:57:23 EST
Article-I.D.: sol.4039
Posted: Mon Nov  9 06:57:23 1987
Date-Received: Wed, 11-Nov-87 04:49:43 EST
References: <2023@homxc.UUCP>
Organization: U of Rochester, CS Dept., Rochester, NY
Lines: 23
Keywords: Mark Williams C, Fseek, fseek
Summary: F-funcs like UNIX sys calls, f-funcs *are* STDIO library routines

In article <2023@homxc.UUCP>, jdn@homxc.UUCP (J.NAGY) writes:
> The functions Fseek, fseek (and Fread, fread, Fwrite, fwrite, etc.)
> seem to perform essentially equivalent functions.
> Is there a prefered choice?  How do you choose?

The capital F functions are GEMDOS functions, similar but not
identical to UNIX system calls.  That is, Fread is similar to read,
Fseek is similar to lseek.

The little f functions are STDIO library functions, identical to
standard IO library functions everywhere.  (Or at least as close
as MW could make them.)  That is, fread under MWC on an Atari does
exactly what fread under UNIX on a VAX does.

If you want to write portable code, I suggest using the little f
functions from the standard IO library.  They're standard. :-)

If you need more control over exactly what it going on, use the
capital F functions from GEMDOS.  If you port something that close
to the machine, changing a function name from "Fssek" to "lseek" will
be the least of your problems.

Stu Friedberg  {ames,cmcl2,rutgers}!rochester!stuart  stuart@cs.rochester.edu