3 ms·
Wow. That's full of falsehoods like these: "What happens is that variable i is converted to unsigned integer." No: 'long i' is converted to 'unsigned long'. "
by cjensen 13y ago
Wow. That's full of falsehoods like these:
"What happens is that variable i is converted to unsigned integer." No: 'long i' is converted to 'unsigned long'.
"Usually size_t corresponds with long of given architecture." No: For example, on Win64 size_t is 64 bits whereas long is 32 bits.
If you're going to write about Advanced Programming, you should be careful to actually be correct.
- ahy1 13y ago> Wow. That's full of falsehoods like these: > "What happens is that variable i is converted to unsigned integer." No: 'long i' is converted to 'unsigned long'. Actually, unsigned long is an unsigned integer. He didn't write unsigned int. > "Usually size_t corresponds with long of given architecture." No: For example, on Win64 size_t is 64 bits whereas long is 32 bits. "Usually" is the keyword here. He could have said "Usually size_t has at least the same amount of bits as long" and it would be better related to the referred rule.
- zurn 13y agoThe "short" long is fantastically tasteless, it's not like source compatiblity with Win16 is has resulted in 64-bit builds of apps appearing.
- pfacka 13y agoI agree that wording is bit unclear. I will try to find better one, thanks.