Thread: convert from size_t to unsigned int

Depends. size_t will probably be 16-bits on a 16-bit system, 32-bits on a 32-bit system, and 64-bits on a 64-bit system. On 64-bit systems, an int is generally going to stay at 4 bytes.

I wouldn't bank on such things, but I also wouldn't bank on an int being able to hold a size_t value. Just use size_t as a data type when you need to work with sizes and don't bother with the conversions if you want to do purely portable code between different architectures.

That warning SPECIFICALLY says that "size_t" and "int" (or "unsigned int") aren't the same size, so obviously, your assumption about them being the same size is NOT true in this case.

You will find that if you look in crtdbg.h, that there are TWO places where size_t is defined, one place where it's defined to "_W64 unsigned int" and once where it is defined as "unsigned __int64".

Edit: I do agree with the idea of "if it comes as a size_t why not keep it as size_t" - almost all compilers[1] support the concept of a size_t. Why convert it?

[1]The type is usually part of the "support files", rather than something that the compiler actually "knows" inherently, but it is part of any moder C standard, and it's a good way to ensure that your "size" variables are big enough!

--
Mats