home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!sdd.hp.com!uakari.primate.wisc.edu!ames!riacs!pan.arc.nasa.gov!roelofs
- From: roelofs@pan.arc.nasa.gov (Greg Roelofs)
- Newsgroups: comp.os.os2.programmer
- Subject: Re: SHORT, USHORT, and other absurdities
- Message-ID: <1992Aug23.044105.8994@riacs.edu>
- Date: 23 Aug 92 04:41:05 GMT
- References: <19920811.003756.988@almaden.ibm.com> <910@nazgul.UUCP> <qr+nf3a.feustel@netcom.com>
- Sender: news@riacs.edu
- Organization: University of Chicago
- Lines: 21
-
- feustel@netcom.com (David Feustel) writes:
-
- >I've often wished that the following typdefs had been included in C:
- >
- >typedef unsigned char U08;
- >typedef signed char I08;
- >typedef unsigned short int U16;
- >typedef signed short int I16;
- >typedef unsigned int U32;
- >typedef int I32;
- >Typedef unsigned long int U64;
- >Typedef long int I64;
- >typedef signed int I32;
- >typedef float F32;
- >typedef double F64;
-
- But what will you do on a machine where shorts are 64 bits by default,
- but can be 24 or 46 bits via a compiler switch? Likewise for 64-bit
- floats and 128-bit doubles?
-
- Greg
-