Newsgroups: comp.lang.c
Path: utzoo!utgpu!watserv1!watmath!datangua
From: datangua@watmath.waterloo.edu (David Tanguay)
Subject: Re: What breaks? (was Re: 64 bit longs?)
Organization: University of Waterloo
Date: Mon, 21 Jan 91 11:39:42 GMT
Message-ID: <1991Jan21.113942.24379@watmath.waterloo.edu>
References: <1991Jan15.202123.14223@gjetor.geac.COM> <14890@smoke.brl.mil> <1991Jan18.044948.27943@zoo.toronto.edu> <14896@smoke.brl.mil> <1991Jan21.025706.7152@zoo.toronto.edu>
Lines: 14

In article <1991Jan21.025706.7152@zoo.toronto.edu> henry@zoo.toronto.edu (Henry Spencer) writes:
|>>There is no portable way to declare a type with *exactly* 32 bits, ...
|>And there is no guarantee that such a type even exists...
|In that case, that machine is going to have real trouble declaring, say,
|a TCP header structure.  It is always possible to find machines so badly
|broken that you can't cope with them.

What about 36 bit machines? Or did you really mean "at least" 32 bits,
and not "exactly"? If the TCP software requires an (non-bitfield) integral
type of exactly 32 bits then it is the TCP software that is broken.
There should be no problem with slop bits in the internal representation
of the structure.
-- 
David Tanguay            Software Development Group, University of Waterloo
