On Wed, 23 Jul 2014 07:07:25 -0400 Richard Hipp <[email protected]> wrote:
> Hex literals are useful in conjunction with the bit-wise AND and OR > operators (& and |) and in applications that make use of bit fields. ... > The current SQLite implementation (on the "hex-literal" branch) works > by converting hex literals of 64 bits or less into a signed 64-bit > integer. Hex literals of 65 bits or more are approximated by a nearby > floating-point number. Hex literals are used in an integer context. Converting them to floating point is counter-productive. If someone gives you a 17-digit hexadecimal literal, he doesn't want a floating point approximation. He wants an error message. I would raise an error for anything over 64 bits, or just ignore it, until you support a processor with a wider integral type. I don't see a need for it except as input to the parser. I guess that puts me in the #6 camp, too. --jkl _______________________________________________ sqlite-users mailing list [email protected] http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
