Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!caen!uwm.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: <1991May4.202850.15034@ux1.cso.uiuc.edu> Date: 4 May 91 20:28:50 GMT References: <168@shasta.Stanford.EDU> <4068@inews.intel.com> <1991May1.023356.8048@trl.oz.au> <5535@goanna.cs.rmit.oz.au> Organization: University of Illinois at Urbana Lines: 18 rockwell@socrates.umd.edu (Raul Rockwell) writes: >seems rather silly to break the compiler just because of old code... And it seems rather silly to prevent NEW code from being GOOD code just because of old code... New compilers can be made to have different modes, one for old traditional code, and one for new modern portable standard and possibly extended code. The only time you'd need that is when you are porting old code to a new machine and are not expecting to get the full benefit of the new machine (such as using only 32 bit operations on a 64 bit machine... ick). -- /***************************************************************************\ / Phil Howard -- KA9WGN -- phil@ux1.cso.uiuc.edu | Guns don't aim guns at \ \ Lietuva laisva -- Brivu Latviju -- Eesti vabaks | people; CRIMINALS do!! / \***************************************************************************/