Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!caip!sri-spam!nike!ucbcad!ucbvax!jade!eris!mwm From: mwm@eris.berkeley.edu Newsgroups: net.micro.amiga Subject: Re: Re: Orphaned Response Message-ID: <952@jade.BERKELEY.EDU> Date: Tue, 8-Jul-86 15:30:02 EDT Article-I.D.: jade.952 Posted: Tue Jul 8 15:30:02 1986 Date-Received: Thu, 10-Jul-86 01:09:16 EDT References: <8607040632.AA22409@pavepaws> Sender: usenet@jade.BERKELEY.EDU Reply-To: mwm@eris.UUCP () Organization: Missionaria Phonibalonica Lines: 18 In article <8607040632.AA22409@pavepaws> dillon@PAVEPAWS.BERKELEY.EDU (Matt Dillon) writes: > I Believe K & R define shorts and longs to be not less than 16 and >32 bits respectively. Sorry, Matt, but K&R defines shorts to be no longer than ints, and longs to be no shorter than ints. I once worked on a "K&R" compiler with 18 bit ints, longs and shorts (I forget, but I think bytes were 18 bits long also!). The ANSI standards adds the restrictions you speak of - shorts at least 16 bits, and longs at least 32 bits. This implies that ints are also at least 16 bits. Of course, the standard only tells you how to choose the smallest portable size to hold a value. It doesn't tell you how to choose the fastest. That should be ints, but...