Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!think.com!zaphod.mps.ohio-state.edu!caen!news.cs.indiana.edu!ux1.cso.uiuc.edu!phil
From: phil@ux1.cso.uiuc.edu (Phil Howard KA9WGN)
Newsgroups: comp.lang.c
Subject: Re: 64 bit architectures and C/C++
Message-ID: <1991May8.215210.18207@ux1.cso.uiuc.edu>
Date: 8 May 91 21:52:10 GMT
References: <168@shasta.Stanford.EDU> <45690005@hpcupt3.cup.hp.com>
Organization: University of Illinois at Urbana
Lines: 19

shankar@hpcupt3.cup.hp.com (Shankar Unni) writes:

>Well, lint goes a long way towards pointing out int-long mismatches, etc.
>But in my (humble?) opinion, much trouble would be headed off if C compilers
>on 64-bit architectures would simply dispense with the 16-bit type and make
>sizes of int == long == void * == 64 bits, and short == 32 bits.  Why is it
>so terribly important to have a 16-bit data type?

That DOUBLES the size of a program that is loading and working with
digitized audio samples that are moer than 8 bits wide.

>In any case, memory is getting cheaper these days..

And software is getting bigger just as fast to fill it up.
-- 
 /***************************************************************************\
/ Phil Howard -- KA9WGN -- phil@ux1.cso.uiuc.edu   |  Guns don't aim guns at  \
\ Lietuva laisva -- Brivu Latviju -- Eesti vabaks  |  people; CRIMINALS do!!  /
 \***************************************************************************/