Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!topaz!nike!ucbcad!ucbvax!decvax!decwrl!glacier!Navajo!rokicki
From: rokicki@Navajo.UUCP
Newsgroups: net.micro.amiga
Subject: Re: short/long/int
Message-ID: <732@Navajo.ARPA>
Date: Tue, 8-Jul-86 22:33:01 EDT
Article-I.D.: Navajo.732
Posted: Tue Jul  8 22:33:01 1986
Date-Received: Thu, 10-Jul-86 01:21:35 EDT
References: <928400002@ico> <500001@hpfcdc.HP.COM>
Organization: Stanford University
Lines: 15

About short/long/int . . .

I use typedef's to solve all these problems.  I will use int's when I
need at least sixteen bits because the int is often faster than either
of the other two, but all the rest of the time I use my own types
exclusively.  Then, to port, you simply change a few typedefs.  (I've
moved over 30,000 lines of code from a VAX Berkeley 4.2 system to the
Amiga with no trouble because of this . . .)  Whenever I want the
arithmetic to be performed with more than 16 bits, and the operands are
ints or smaller, I always coerce . . . it *might* make the program
slightly slower, but I haven't noticed it.

Now the question:  Why haven't I seen this in any other code?

-tom