Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!panda!teddy!jpn
From: jpn@teddy.UUCP (John P. Nelson)
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: pointer alignment when int != char *
Message-ID: <4329@teddy.UUCP>
Date: Fri, 4-Sep-87 10:46:49 EDT
Article-I.D.: teddy.4329
Posted: Fri Sep  4 10:46:49 1987
Date-Received: Sat, 5-Sep-87 17:39:24 EDT
References: <493@its63b.ed.ac.uk> <6061@brl-smoke.ARPA> <3812@spool.WISC.EDU> <26910@sun.uucp> <625@sugar.UUCP>
Reply-To: jpn@teddy.UUCP (John P. Nelson)
Organization: GenRad, Inc., Concord, Mass.
Lines: 13
Xref: mnetor comp.lang.c:4158 comp.unix.wizards:4080

In article <625@sugar.UUCP> peter@sugar.UUCP (Peter da Silva) writes:
>> The standard should NOT address this.  The standard mentions neither "lseek"
>
>Are you saying that the ANSI 'C' library includes all the UNIX date/time
>functions, but doesn't include lseek?

The Draft Standard does not include any of the UNIX low-level io functions
(read/write/open/close) including lseek.  Fseek IS supported.

The rationale says something to the effect that the low level functions
are 1. redundant, 2. not necessarily any more efficient than the FILE
based functions.  They do mention the POSIX standard, and that those
functions will be defined there.