If the size of the int is that important one can use int16_t, int32_t and int64_t (need the iostream include for that if I remember correctly). What's nice about this that int64_t should not have issues on a 32bit system (this will impact the performance though). In this case, depending upon what your use case is, you might be better off using int (or long long) for s1 and s2.
There are some functions in C/POSIX that could/should use size_t, but don't because of historical reasons. For example, the second parameter to fgets should ideally be size_t, but is int. How can I see the size of files and directories in Linux? If use df -m, then it shows the size of all the directory at the top level, but, for the directories and files inside the directory, how do I 82 size_t is the result type of the sizeof operator.
What Size Needle Do They Use When You Donate Blood, Use size_t for variables that model size or index in an array. size_t conveys semantics: you immediately know it represents a size in bytes or an index, rather than just another integer. Also, using size_t to represent a size in bytes helps making the code portable. Just use the sys.getsizeof function defined in the sys module. sys.getsizeof(object[, default]): Return the size of an object in bytes.
What Size Needle Do They Use When You Donate Blood, The object can be any type of object. All built-in objects will return correct results, but this does not have to hold true for third-party extensions as it is implementation specific. Only the memory consumption directly attributed to the object is accounted ... In several C++ examples I see a use of the type size_t where I would have used a simple int. What's the difference, and why size_t should be better?
