On Wed, 12 Jun 2019 18:40:19 -0400 Richard Hipp <d...@sqlite.org> wrote:
> On 6/12/19, James K. Lowden <jklow...@schemamania.org> wrote: > > what kind of computation > > would lead to a value in memory representing -0,0? > > 0.0/-1.0 Fine. I suspect the reason -0.0 has never cropped up as an issue in my experience is that -0.0 == 0.0. The existence of -0.0 never mattered because it was computationally irrelevant. I couldn't tell from your reference to Wolfram whether or not you considered the "negative zero is not math" to be dispositive (so to speak). If you're still considering rendering "-0.0" in the even the floating point unit happened to end up with "negative zero", are you also going to provide a way for users to detect the sign bit and "positivize" zero, such as through a SQLite function for signbit(3)? If so, to what end? IMO this whole discussion is a tempest in a teapot about angels dancing on the head of a pin. I have yet to see anyone offer any advantage of treating -.0.0 as anything other than 0. Far more important is integer division by zero. SQLite disguises it as NULL, making it undetectable and indistinguishable from genuinely missing information. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users