FloatVer 2.0

FloatVer gets a breaking change.

FloatVer 2.0

A massive update to FloatVer 1.0 has been brewing for a while but it's finally ready for launch.

Whereas FloatVer 1.0 uses IEEE754 32-bit non-negative values, FloatVer 2.0 uses IEEE754 64-bit non-negative values. That's it, that is the only difference.

This means you have more values to choose from and your version numbers can be bigger (a lot bigger).

Most significantly, FloatVer 2.0 is compatible with a wider range of programming languages, making adoption an easy choice. Most people should use FloatVer 2.0 as 64-bit floating point values are standard on most platforms. If in doubt, choose FloatVer 2.0.

By FloatVer's own definitions, this is a breaking change because a 64 bit float takes up more than 1.5 times as much space as a 32 bit float.

FloatVer 2.0 semantics

The rules of FloatVer 2.0 are exactly the same as they are for FloatVer 1.0, but now you have twice as many bits for extended precision and range.

  • 0.0 is still the smallest FloatVer value (just like in FloatVer 1.0)
  • The largest version you can use in FloatVer 2.0 is: 179769313486231570814527423731704356798070567525844996598917476803157260780028538760589558632766878171540458953514382464234321326889464182768467546703537516986049910576551282076245490090389328944075868508455133942304583236903222948165808559332123348274797826204144723168738177180919299881250404026184124858368.0

Erratum/apology

If anyone was confused by the April 1st joke now infamously known as Rational FloatVer, we apologize. FloatVer does not use rational numbers and there is no intention to ever try. For everyone else, we hope you enjoyed the joke.