...> Assuming all the values of int are in the range of unsigned char, what happends if getc returns EOF?... that EOF was the value of the byte read? Does that mean that code aiming ... getc() returned EOF, consider EOF a valid byte read) To me, that seems to be ...bit, and am still doing a lot of work on a platform where char, int, and short are all 16 bits. I just want to ...

... values of int are in the range of unsigned char, what happends if getc returns EOF? Is it possible that EOF was the value of the byte read? Does that mean that code aiming for... getc() returned EOF, consider EOF a valid byte read) To me, that seems to be ...-bit, and am still doing a lot of work on a platform where char, int, and short are all 16 bits. I just want to ...

...(defined in Yes but I can change it to accept 'unsigned char' if that is more efficient. I have no idea what sender... exactly does in your system. If for you size matters, you should use 'unsigned char' of course, because 'unsigned char' is 1 byte, while 'int' is 4 bytes (at least on Windows 32-bit platform). Here I would put at least an assert (ASSERT macro, or whatever),...

...th_off are replaced. Then the 4 bytes are written back. But should (...ia64/itanium On FreeBSD Tier 1 platforms, the access is probably going to...are always accessed as integers => 4-byte access But th_x/th_off may not... into the treatment of the "char" type. Most modern C compilers ... "unsigned char". Does this really change the access to 1-byte? As in "Programming in C" ...

.... Because in this way always 4 bytes are read and the the bits of th_off are replaced. Then the 4 bytes are written back. But should (th_x and th_off) not only be 1 byte in whole -> only read and ... code on? On FreeBSD Tier 1 platforms, the access is probably going to ... dependency into the treatment of the "char" type. Most modern C compilers support "unsigned char".

...> address and '&' operator is not applicable for bit fields. I initialized all the members as unsigned char. As the standard goes, a char is always 1 byte. Yes, a char is always 1 byte, but a byte is not always 8 bits. But you're probably safe in assuming that it is on most platforms. -- Keith Thompson (The_Other_Keith) kst-u@mib.org <http://www.ghoti.net/~...

... binary representation, particularly with regards to byte order. If you want to be...CLASS WILL NOT BE READABLE // ON PLATFORM APART FROM THE ONE THEY ARE... #endif BOOST_ARCHIVE_OR_WARCHIVE_DECL(void) save(const char * t); BOOST_ARCHIVE_OR_WARCHIVE_DECL(void) save(const wchar_t...(serialization::array<ValueType> const& a, unsigned int) { save_binary(a.address(),a....

... what characters would be printed. Exotic platforms have integrals with padding (I think only the unsigned ones are allowed to that, the...standard. The standard says that the unsigned integral values (that is even for ...sign. Then there are alot of platform specific details, such as the size of a byte (in...first you can use std::numeric_limits<unsigned char>::digits. For the second of...

..., by the way. On all platforms supported by the diet libc, ...could be 0L (long int), 0UL (unsigned long int), etc.). Converting 0 to... subtile breakage, though. Does a platform where 0 != NULL is true ...the ANSI standard even allow such platforms? The representation of a null ... 0.0? Are all bytes of char array 0x00? What about ...(NULL pointer, 0 float, 0 byte, 0 int). Good, that's ...

...) that the definition of a byte was the smallest object that the...because of historical reasons) instead of char* but it says it writes/... can work with std::vector<char> buffers because I know a ... I cannot do that with "unsigned char" buffers because from what ... with treating the platform bytes as pure unsigned integrals because once ... is signed on the current platform), some values may appear as ...