This is a discussion on Re: char signed or unsinged ? (was Netscape 7 issues) within the Sun Solaris Administration forums, part of the Solaris Operating System category; --> In article <bf1ccq$mg6$1@news.cs.tu-berlin.de>, Joerg Schilling <js@cs.tu-berlin.de> wrote: >In article <bf1ae5$qe1@keck5.umd.edu>, >Eric J. Kostelich <ejk@Glue.umd.edu> wrote: > >But limits.h is ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| In article <bf1ccq$mg6$1@news.cs.tu-berlin.de>, Joerg Schilling <js@cs.tu-berlin.de> wrote: >In article <bf1ae5$qe1@keck5.umd.edu>, >Eric J. Kostelich <ejk@Glue.umd.edu> wrote: > >But limits.h is a SysV file and not a standard file. No. limits.h has always been a standard header in ANSI C. >Better is to include inttypes.h and use uint8_t & int8_t Maybe. But inttypes.h exists only in C99, not in earlier standards. In addition, implementations MUST NOT define uint8_t and int8_t if the processor does not have a native signed and unsigned integer type that's exactly 8 bits wide. The most portable way (in C99, anyway) is to use uint_least8_t and int_least8_t (or uint_fast8_t and int_fast8_t). --Eric |
| Thread Tools | |
| Display Modes | |
|
|