IMO, when acting as a storage engine, SQLite should be good to the last bit. The sign of zero, the least significant bit of any mantissa, and the payload bits of NaN should all be returned exactly as they were stored.
The history of almost-but-not-quite-IEEE754 arithmetic has been convergence towards fully-IEEE754 pretty much everywhere. People who are serious about floating-point rely on its features. Even though serious users are quite a bit smaller than the community of casual floating-point users, the maintenance burden of maintaining two sets of semantics means that you're better off just supporting IEEE754. For an SQL engine, the next-best-thing to strict binary IEEE754 is not sloppy binary IEEE754, its probably strict decimal IEEE754. On Wed, Jun 12, 2019 at 7:35 AM Richard Hipp <d...@sqlite.org> wrote: > IEEE754 floating point numbers have separate representations for +0.0 > and -0.0. As currently implemented, SQLite always display both > quantities as just "0.0". > > Question: Should SQLite be enhanced to show -0.0 as "-0.0"? Or, > would that create unnecessary confusion? > > -- > D. Richard Hipp > d...@sqlite.org > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > -- Jonathan Brandmeyer Vice President of Software Engineering PlanetiQ _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
