I think that compilers use different types for defining size_t (and other defined types in C standard library) according to the environment bit depth.
So, for example, if I write a code for a 32-bit computer, size_t can be unsigned int, but if I write a code for a 64-bit computer, then size_t can be unsigned long ...it is so?
Do compilers define the type of size_t automatically according to the chosen type of projects?
This may be of interest : The GNU C Library: Important Data Types
Yes.Originally Posted by KemalT
Compliers don't know what a "project" is, you're probably thinking of an IDE. But either way, yes, compliers and IDEs usually compile to the platform you're compling on.
The size_t is implementation defined type so yes different compilers can and do define this using different undefined types. By the way it is not necessarily related to the number of "bits" of the computer. For example a 32bit compiler could define the size_t as an unsigned long if it so desired.So, for example, if I write a code for a 32-bit computer, size_t can be unsigned int, but if I write a code for a 64-bit computer, then size_t can be unsigned long ...it is so?
And remember all the integral types have implementation defined maximums. The standard only says that the maximums must be at least so large. For example an int must be able to hold values of at least 32767.
Jim
Thanks a lot to all ...
Then, I think that there are two or more related header files for those type definitons and the compiler uses the appropriate one for intended computer architecture when compiling the code ... right?
Last edited by KemalT; 02-09-2015 at 12:35 PM.
With Visual C++, even 64-bit applications use a 32-bit value for type long. To get 64-bits, you need to use long long on VC++. The main thing about the size of size_t, that you can count on, is that sizeof(size_t) >= sizeof(void*).
What can this strange device be?
When I touch it, it gives forth a sound
It's got wires that vibrate and give music
What can this thing be that I found?
