Why is size_t unsigned?

by

size_t is unsigned for historical reasons.

On an architecture with 16 bit pointers, such as the “small” model DOS programming, it would be impractical to limit strings to 32 KB.

For this reason, the C standard requires (via required ranges) ptrdiff_t, the signed counterpart to size_t and the result type of pointer difference, to be effectively 17 bits.

Those reasons can still apply in parts of the embedded programming world.

However, they do not apply to modern 32-bit or 64-bit programming, where a much more important consideration is that the unfortunate implicit conversion rules of C and C++ make unsigned types into bug attractors, when they’re used for numbers (and hence, arithmetical operations and magnitude comparisions). With 20-20 hindsight we can now see that the decision to adopt those particular conversion rules, where e.g. string( "Hi" ).length() < -3 is practically guaranteed, was rather silly and impractical. However, that decision means that in modern programming, adopting unsigned types for numbers has severe disadvantages and no advantages – except for satisfying the feelings of those who find unsigned to be a self-descriptive type name, and fail to think of typedef int MyType.

Summing up, it was not a mistake. It was a decision for then very rational, practical programming reasons. It had nothing to do with transferring expectations from bounds-checked languages like Pascal to C++ (which is a fallacy, but a very very common one, even if some of those who do it have never heard of Pascal).

More Related Contents:

  1. unsigned int vs. size_t
  2. When to use std::size_t?
  3. A warning – comparison between signed and unsigned integer expressions
  4. Overflowing of Unsigned Int
  5. Does “std::size_t” make sense in C++?
  6. Cross platform format string for variables of type size_t? [duplicate]
  7. What is going on with bitwise operators and integer promotion?
  8. Difference between size_t and std::size_t
  9. Should I include stddef.h or cstddef for size_t
  10. C++ Implicit Conversion (Signed + Unsigned)
  11. How can I safely average two unsigned ints in C++?
  12. Strcmp() function not working properly [closed]
  13. Can num++ be atomic for ‘int num’?
  14. What’s the difference between assignment operator and copy constructor?
  15. C++11 reverse range-based for-loop
  16. How do I start a new CUDA project in Visual Studio 2008?
  17. Why is the C++ initializer_list behavior for std::vector and std::array different?
  18. Instantiate class from name?
  19. how to check whether two matrices are identical in OpenCV
  20. Are C++ Templates just Macros in disguise?
  21. Most efficient/elegant way to clip a number?
  22. How to append a char to a std::string?
  23. Writing robust (color and size invariant) circle detection with OpenCV (based on Hough transform or other features)
  24. Why doesn’t C++ support named parameters?
  25. Why can’t std::ostream be moved?
  26. Problems with running EXE file built with Visual Studio on another computer
  27. Purpose of a “.f” appended to a number?
  28. What is the difference between if (NULL == pointer) vs if (pointer == NULL)?
  29. Why should I prefer to use member initializer lists?
  30. How do I initialize a const data member?

Leave a Comment