Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!ut-sally!husc6!rutgers!ames!lll-tis!ptsfa!hoptoad!academ!uhnix1!sugar!peter
From: peter@sugar.UUCP (Peter da Silva)
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: pointer alignment when int != char *
Message-ID: <656@sugar.UUCP>
Date: Sat, 5-Sep-87 22:17:15 EDT
Article-I.D.: sugar.656
Posted: Sat Sep  5 22:17:15 1987
Date-Received: Wed, 9-Sep-87 05:43:54 EDT
References: <493@its63b.ed.ac.uk> <6061@brl-smoke.ARPA> <3812@spool.WISC.EDU> <27183@sun.uucp>
Organization: Sugar Land UNIX - Houston, TX
Lines: 13
Summary: But fseek *is* in the standard.
Xref: mnetor comp.lang.c:4218 comp.unix.wizards:4135

> a system, "read" and "write" would have to perform the same sort of translation
> on data in order to make UNIX programs work without change, "lseek" would have
> to work with cookies rather than byte offsets, and if you wanted to be able to
> use "read" or "write" to get at the "raw" binary data in the file, you'd have
> to have a text/binary flag on "open", or something such as that.

I have no problem with any of that. On systems where it is not appropriate
to use read() and write() as the primitives, implement them using fread()
and fwrite(). There is certainly a precedent for having flags on open(),
too.
-- 
-- Peter da Silva `-_-' ...!seismo!soma!uhnix1!sugar!peter
--                 'U`  <-- Public domain wolf.