And here is the same code in unit/module form with tables commented out: The possible table lookups/optimizations are left in in case I or any one else wants to test those ;) // *** Begin of Module Code *** unit UnitStringToUint64_version_003; interface function TryStrToUint64( S : string; var Value : Uint64 ) : boolean; implementation { Skybuck's TryStrToUint64 conversion

Hello, Sometimes I google for my own code and then it sucks if I one can't find it or too it's incomplete. So one more time the complete code as it now is, all 3 versions embedded. Version 0.03 is now active... big 1600 bytes lookup tables still active but those could be commented out. Maybe somebody else could write a nice benchmark program for it ? Tomorrow maybe I write one, but

actually, it doesn't store it in hex, it stores it in binary, with an implied high-order bit. Since a normalized floating-point number ALWAYS has a 1 in the high order position, that is assumed, and the first mantissa bit we see is actually the SECOND mantissa bit, since the first bit is always implied. IBM got into trouble with numerical analysts when they introducted the /360, because it