Hi, When using the conversion "bullets" to convert SGL, DBL and EXT to integers there are some values which convert wrong. One example is the integer 9223370937343148030, which can be represented exactly as a SGL (and thus exactly as DBL and EXT as well). If you convert this to I64 you get 9223370937343148032 instead, even though the correct integer is within the range of an I64. There are many similar cases, all (I've noticed) within the large end of the ranges. This has nothing to do with which integers can be represented exactly as a floating point value or not. This is a genuine conversion bug mind you. Cheers, Steen

Hi Steen, Thanks for identifying this. I have confirmed the EXT to U64 conversion problem by simply attempting to round-trip a U64 value xFFFFFFFFFFFFF9B0 to EXT and back, getting xFFFFFFFFFFFFFFFF as a result (and the intermediate EXT value is correct). The problem seems to be restricted to integer values with all of the top 53 bits set, along with one or more of the lowest 11. I have reported this (#396305), along with the limited display precision issues (#396337). Jim

LabVIEW

BUG: Large floating point numbers convert to the wrong integer

Solved!

CAR 396305 discussed in this thread has been fixed in LabVIEW 2013. For a more complete list of bugs fixed in LabVIEW 2013, check the LabVIEW 2013 Bug Fixes. You can download an evaluation copy of LabVIEW 2013 at http://www.ni.com/trylabview/ or if you have an earlier version of LabVIEW installed and an active SSP subscription, you will be able to download the latest version of LabVIEW through NI Update Service.

Jeff Peacock

Product Support Engineer | LabVIEW R&D | National Instruments