Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!jade!ucbcad!ames!hao!oddjob!mimsy!cvl!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: 32bit = 16bit x 16bit
Message-ID: <6607@brl-smoke.ARPA>
Date: Thu, 29-Oct-87 23:32:57 EST
Article-I.D.: brl-smok.6607
Posted: Thu Oct 29 23:32:57 1987
Date-Received: Wed, 4-Nov-87 05:33:36 EST
References: <1912@gryphon.CTS.COM> <3294@sol.ARPA> <2545@cbmvax.UUCP> <2565@cbmvax.UUCP> <2262@sfsup.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <2262@sfsup.UUCP> mpl@sfsup.UUCP (M.P.Lindner) writes:
>3. as for the people who say "Never use the basic types", I say the following:

Mike gave good advice -- heed it.

One additional note:  ANSI C will guarantee minimum sizes for the
basic integer data types.  If you KNOW that all values will fit in
a minimum implementation of the data type, you can use it when
storage space is a significant factor.  Otherwise, (int) is usually
the type that is the fastest; however, it may be only 16 bits long
so if that isn't enough for your application you have no choice but
to use long (guaranteed to be at least 32 bits).  If a long isn't
enough, you'll have to find or develop a multiple-precision package
and pay the speed penalty.