Xref: utzoo comp.unix.sysv386:8300 comp.lang.c:39476
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!crdgw1!pegasus!toy
From: toy@pegasus.crd.ge.com (Raymond L. Toy)
Newsgroups: comp.unix.sysv386,comp.lang.c
Subject: Re: time(0L) - history of a misconception (was Re: SCO password generator)
Message-ID: <19810@crdgw1.crd.ge.com>
Date: 22 May 91 21:17:46 GMT
References: <1991May14.040042.15199@jpradley.jpr.com> <588@sherpa.UUCP> <1141@mwtech.UUCP> <4138@uc.msc.umn.edu>
Sender: news@crdgw1.crd.ge.com
Reply-To: toy@pegasus.crd.ge.com (Raymond L. Toy)
Followup-To: comp.unix.sysv386
Lines: 31


In article <4138@uc.msc.umn.edu> you write:
|> In article <1141@mwtech.UUCP> martin@mwtech.UUCP (Martin Weitzel) writes:
|> >In article <588@sherpa.UUCP> rac@sherpa.UUCP (Roger Cornelius) writes:
|>[...]
|> 
|> You are right -- to ensure portability, you should always pass what
is expected
|> (i.e. a pointer and not a long).  This way, if someday a machine is created 
|> on which a pointer to a long is a different size then a long, the
program will
|> still work.  However, I don't know of any machines on which the two differ.

Such machines do exist and are very common.  In particular, a PC has
this property when using the small memory model: a pointer is 16 bits
long, but a long is 32 bits.

Also, at school, we had a Harris H800 mini, a 24-bit machine.  A
pointer was 24 bits long (really only 22!!!), and a long was really 47
bits long!!!!  This was a rather bizarre machine, to say the least.
It's dead and gone now, fortunately.

Ray
ray ----> toy@soho.crd.ge.com

|> 
|> -Jeff
|> ---
|> Jeff Turner                           EMAIL: jeff@msc.edu
|> Minnesota Supercomputer Center, Inc.  VOICE: (612) 626-0544
|> Minneapolis, Minnesota  55415           FAX: (612) 624-6550