time(0L) - history of a misconception (was Re: SCO password generator)

Conor O'Neill conor at lion.inmos.co.uk
Thu May 23 19:27:10 AEST 1991


In article <4138 at uc.msc.umn.edu> jeff at uf.UUCP (Jeff Turner) 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.

Think of a 16-bit machine, where pointers are 16-bits, but longs are 32-bits.
Not a particularly obscure possibility.

(Oh - by the way - we sell one - the IMS T222 transputer).

---
Conor O'Neill, Software Group, INMOS Ltd., UK.
UK: conor at inmos.co.uk		US: conor at inmos.com
"It's state-of-the-art" "But it doesn't work!" "That is the state-of-the-art".



More information about the Comp.unix.sysv386 mailing list