compiler error with size_t

[Jane Heng]

Quote: "In GNU system size_t is equivalent to either unsigned int or unsigned long int.

If the system header files declare malloc with an argument of type size_t and you declare malloc with an argument of type unsigned int, you will get a compilation error if size_t happens to be unsigned long int on your system.

To avoid any possibility of error, when a function argument or value is supposed to have type size_t, never declare its type in any other way."

Can anyone give me an example of what does the last quote sentence means by avoiding compiler errors or how then a compiler error will occur with the size_t.

Thanks

[donbock]

If you're supposed to use size_t, then use size_t.

You may think you know that size_t is really the same as unsigned int, but you're wrong. It may be the same as unsigned int for the compiler you're using today; but it may be unsigned long for the compiler you use tomorrow.