tree 280f3baea77726cdbd5cd93636e8523689f1cf77
parent 5defb4ed1a4293b8e2bf641e16b156fb9de498cc
author Tero Kinnunen <tero.kinnunen@gmail.com> 1639533628 +0200
committer GitHub <noreply@github.com> 1639533628 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhuUw8CRBK7hj4Ov3rIwAACccIACDfXC7yTA5lP4hViuRli+D/
 hjDzuKZP4tnYPX3Bdy2rUCQKMVyejQcLqwLv8yQCR/ItY9fUSv9JZj1ETMZl8oP5
 YcPnFKPcgxsumvJPudPHJ0xhYdjfZdmx2I+aX12DhJfp7kV7ODBTQdTExrX1+/BH
 By07cv2MjmADydI3aHz7hvkmfZgvKrk27JJG7tTvMkPkmE1l1c4Zq4EeXQB9KiOe
 Ph5GJwR4FlpGbPu2k6Iz5ZOpgdY+beorRdb6qbDjTOEv3yu/41TR+MkJhK0C/ZHf
 /z46K6MKsyla4yT2AMqj0zvlgMsOUT05mem0iryd/vh6EWC7Cd+aS7dJRYb6Tno=
 =tbJj
 -----END PGP SIGNATURE-----
 

Parse large floats as infinity (#1349) (#1353)

Return 1.9.1 functionality where values too large to fit in
double are converted to positive or negative infinity.

Commit 645cd04 changed functionality so that large floats cause
parse error, while version 1.9.1 accepted them as infinite.
This is problematic because writer outputs infinity values
as `1e+9999`, which could no longer be parsed back.

Fixed also legacy Reader even though it did not parse large values
even before breaking change, due to problematic output/parse asymmetry.

`>>` operator sets value to numeric_limits::max/lowest value if
representation is too large to fit to double. [1][2] In macos
value appears to be parsed to infinity.

> | value in *val*           | description |
> |--------------------------|-------------|
> | numeric_limits::max()    | The sequence represents a value too large for the type of val |
> | numeric_limits::lowest() | The sequence represents a value too large negative for the type of val |

[1] https://www.cplusplus.com/reference/istream/istream/operator%3E%3E/
[2] https://www.cplusplus.com/reference/locale/num_get/get/

Signed-off-by: Tero Kinnunen <tero.kinnunen@vaisala.com>

Co-authored-by: Tero Kinnunen <tero.kinnunen@vaisala.com>