Path: utzoo!attcan!uunet!crdgw1!steinmetz!davidsen
From: davidsen@steinmetz.ge.com (Wm. E. Davidsen Jr)
Newsgroups: comp.lang.c
Subject: Re: size of double in Cray C
Message-ID: <13682@steinmetz.ge.com>
Date: 27 Apr 89 19:55:43 GMT
References: <10176@socslgw.csl.sony.JUNET> <12247@lanl.gov> <1989Apr24.172747.993@utzoo.uucp> <8050@boring.cwi.nl> <10112@smoke.BRL.MIL> <8055@boring.cwi.nl> <1989Apr26.170635.3933@utzoo.uucp>
Reply-To: davidsen@crdos1.UUCP (bill davidsen)
Organization: General Electric CRD, Schenectady, NY
Lines: 19

In article <1989Apr26.170635.3933@utzoo.uucp> henry@utzoo.uucp (Henry Spencer) writes:

| The choice being discussed here is not the size of floating point on the
| machine, but the mapping from C's sizes to machine sizes.  There's nothing
| wrong with making "float" and "double" the same size, and this is clearly
| what should have been done.

  As a matter of interest, the only thing on the Cray2 C which has
really bitten me is the 64 bit short. When porting code to the C2 I
found a number of places in which the size of int could vary without
problem, but short>16 bits caused trouble.

The recent net posting of the lzhuf program suffers from this... There's
still at least one place in which truncation to 16 bits is assumed
implicitly, and I hope to find it.
-- 
	bill davidsen		(wedu@crd.GE.COM)
  {uunet | philabs}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me