Why doesn’t C have unsigned floats?

by

Why C++ doesn’t have support for unsigned floats is because there is no equivalent machine code operations for the CPU to execute. So it would be very inefficient to support it.

If C++ did support it, then you would be sometimes using an unsigned float and not realizing that your performance has just been killed. If C++ supported it then every floating point operation would need to be checked to see if it is signed or not. And for programs that do millions of floating point operations, this is not acceptable.

So the question would be why don’t hardware implementers support it. And I think the answer to that is that there was no unsigned float standard defined originally. Since languages like to be backwards compatible, even if it were added languages couldn’t make use of it. To see the floating point spec you should look at the IEEE standard 754 Floating-Point.

You can get around not having an unsigned floating point type though by creating a unsigned float class that encapsulates a float or double and throws warnings if you try to pass in a negative number. This is less efficient, but probably if you aren’t using them intensely you won’t care about that slight performance loss.

I definitely see the usefulness of having an unsigned float. But C/C++ tends to chose efficiency that works best for everyone over safety.

More Related Contents:

  1. Difference between signed / unsigned char [duplicate]
  2. Difference between size_t and unsigned int?
  3. what is the unsigned datatype?
  4. What is time_t ultimately a typedef to?
  5. Where in memory are my variables stored in C?
  6. Dividing 1/n always returns 0.0 [duplicate]
  7. How to get the sign, mantissa and exponent of a floating point number
  8. How to compare double numbers?
  9. What operations and functions on +0.0 and -0.0 give different arithmetic results?
  10. Question about C behaviour for unsigned integer underflow
  11. bit shifting with unsigned long type produces wrong results
  12. Any guaranteed minimum sizes for types in C?
  13. Floating point comparison `a != 0.7` [duplicate]
  14. how to check if the input is a number or not in C?
  15. Representing integers in doubles
  16. What is the fastest way to convert float to int on x86
  17. Why does adding a small float to a large float just drop the small one?
  18. Comparing floating point numbers in C
  19. Comparing float and double in C
  20. Is it safe to assume floating point is represented using IEEE754 floats in C?
  21. Count number of digits after `.` in floating point numbers?
  22. Is there a tool to know whether a value has an exact binary representation as a floating point variable?
  23. plain C: opening a directory with fopen()
  24. How to use C library created by MATLAB Coder codegen in C program with emxArray arguments?
  25. problems in floating point comparison [duplicate]
  26. Is fmod() exact when y is an integer?
  27. Why / when to use `intptr_t` for type-casting in C?
  28. Trouble with float on C [duplicate]
  29. Returning function pointer type
  30. What defines an opaque type in C, and when are they necessary and/or useful?

Leave a Comment