Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!zaphod.mps.ohio-state.edu!samsung!rex!uflorida!gatech!purdue!haven!adm!smoke!gwyn
From: gwyn@smoke.brl.mil (Doug Gwyn)
Newsgroups: comp.lang.c
Subject: Re: What breaks? (was Re: 64 bit longs?)
Message-ID: <14890@smoke.brl.mil>
Date: 17 Jan 91 23:27:48 GMT
References: <54379@eerie.acsu.Buffalo.EDU> <1991Jan15.053356.2631@zoo.toronto.edu> <1991Jan15.202123.14223@gjetor.geac.COM>
Organization: U.S. Army Ballistic Research Laboratory, APG, MD.
Lines: 9

In article <1991Jan15.202123.14223@gjetor.geac.COM> adeboer@gjetor.geac.COM (Anthony DeBoer) writes:
>It seems to me that there really isn't any _portable_ way to declare a 32-bit
>long, for example.

There is no portable way to declare any integral type constrained to use
precisely 32 bits in its representation.  However, "long" portably declares
one that has AT LEAST 32 bits in its representation (or, you could express
this in terms of the guaranteed range of representable values).  net32_t
is hopeless for the first case and unnecessary for the second.