Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: pointer alignment when int != char *
Message-ID: <6397@brl-smoke.ARPA>
Date: Thu, 3-Sep-87 19:09:14 EDT
Article-I.D.: brl-smok.6397
Posted: Thu Sep  3 19:09:14 1987
Date-Received: Sat, 5-Sep-87 12:20:06 EDT
References: <493@its63b.ed.ac.uk> <6061@brl-smoke.ARPA> <3812@spool.WISC.EDU> <26910@sun.uucp> <625@sugar.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 17
Xref: mnetor comp.lang.c:4145 comp.unix.wizards:4064

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

It doesn't include open(), read(), write(), fork(), etc. either.
The reason is that it is probably impossible to specify these
adequately in a common specification for all systems.  Since the
stdio routines ARE specified, there is little need for the
lower-level I/O routines in portable application programming.

The date/time functions are specified in a system-independent way
and are useful in portable applications.  The fact that they
originated in the UNIX C library is largely irrelevant; most of
the library routines in the proposed ANSI C standard did.

lseek(), read(), etc. are specified in IEEE 1003.1 (POSIX),
however, since it specifically addresses just UNIX-like systems.