Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!mandrill!hal!ncoast!allbery
From: allbery@ncoast.UUCP
Newsgroups: comp.lang.c,comp.unix.wizards
Subject: Re: pointer alignment when int != char *
Message-ID: <4469@ncoast.UUCP>
Date: Sat, 5-Sep-87 13:07:41 EDT
Article-I.D.: ncoast.4469
Posted: Sat Sep  5 13:07:41 1987
Date-Received: Sun, 6-Sep-87 10:19:04 EDT
References: <493@its63b.ed.ac.uk> <6061@brl-smoke.ARPA> <3812@spool.WISC.EDU> <26910@sun.uucp> <625@sugar.UUCP>
Reply-To: allbery@ncoast.UUCP (Brandon Allbery)
Followup-To: comp.lang.c
Organization: Cleveland Public Access UN*X, Cleveland, Oh
Lines: 20
Xref: utgpu comp.lang.c:4025 comp.unix.wizards:3826

As quoted from <625@sugar.UUCP> by peter@sugar.UUCP (Peter da Silva):
+---------------
| > 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?
+---------------

We're not talking about UNIX standards, we're talking about C standards.
Date and time are easily convertible under any OS; but how do you implement
a byte-oriented lseek() under VMS?  VM/CMS on an IBM?  (Both use fixed 80-byte
records for text files -- NOT byte streams! -- and other record formats for
non-text files.)
-- 
	    Brandon S. Allbery, moderator of comp.sources.misc
  {{harvard,mit-eddie}!necntc,well!hoptoad,sun!mandrill!hal}!ncoast!allbery
ARPA: necntc!ncoast!allbery@harvard.harvard.edu  Fido: 157/502  MCI: BALLBERY
   <<ncoast Public Access UNIX: +1 216 781 6201 24hrs. 300/1200/2400 baud>>
All opinions in this message are random characters produced when my cat jumped
(-:		      up onto the keyboard of my PC.			   :-)