>>9
that makes sense. could it be that >>6-kun is just spewing the ``don't do anything because the compiler optimizes it'' bullshit without actually shit about it?
Name:
Anonymous2012-09-26 13:44
>>9
The compiler could change the type and still comply with the standard in code like this: for(int i = 0; i < 100; ++i) {
/* some code that doesn't modify or take the address of i */
}
Actually, perhaps they use a non-conservative garbage collector and one of the bits is a type tag. Or the servers are running on a machine whose word size is 31 bits.
>>22
A few languages specify 31-bit integers.
True, it's not the architecture, but >>20 is just a baka. I suspect most dedicated game servers are 64-bit, and have been for quite a few years.
>>26
Are you serious? If you open a file and you count the number of characters on it, it can be any number from 0 to infinity and EOF can't use any of those numbers.
>>29 the number of characters
What does this have to do with anything? When checking for EOF, programs loop through each individual character. That's what it's for.
>>26
Someone could make an I/O library (not stdio compatible) that does this for text files, but binary files need the ability to store any character, including the control characters.
Name:
Anonymous2012-09-27 20:31
>>23
Just because a server uses a 64-bit CPU and OS doesn't mean its users do. Many people still use old CPUs with 32-bit bus widths, and thus still use 32-bit OSes and require 32-bit game clients.