A floating point number will be internally represented by a mantissa and an exponent. This is of course in base 2. The fractional parts of the numbers you show cannot be represented exactly in base 2. Hence there are more binary digits than there are decimal digits and some precision is lost in the conversion process. This is normal. Your solution is the right way to do this.

This question comes up frequently, and not just on Perl websites. The last time I saw the question I spent some time working on a response with the goal of it being more approachable than the standard "What every computer scientist..." article is. I'm so glad I don't have to type it all over again.

You might want to request that your build of Perl get a different number of digits declared as "worth worrying about". Your addition only removes a single digit from the magnitude of the numbers involved. That should not, IMHO, be enough to trigger the showing of such noise.

It would probably be better for your version of Perl to be built to consider 13 digits (or maybe 14) as worth reporting instead of 15.

It looks like modern C compilers define DBL_DIG and Perl defaults to using that when converting a double into a string. Standard "double" has 52 bits of mantissa which gives 15.65 digits of accuracy (not 15.95 like wikipedia seems to claim, including the sign bit in the calculation for unknown reasons). My C compiler defines 15 for DBL_DIG, which makes sense. But Perl should not be caring about so many digits. We need only about 1/2 of a digit of error for "9999999" or "0000001" noise to start showing up.

I would want at least 1.5 digits of slush before such noise results so I would hope that Perl would default to using DBL_DIG-1 (DBL_DIG-2 seems even better) not DBL_DIG (for NV_DIG when NV is a "double").