I suspect part of the reason is accuracy, as well. Base 10 decimals don't necessarily convert to an exact base 2 decimal. 1.2 converts to something like 1.001100110011001100110011....... Storing them as integers, then manipulating them within the code preserves the accuracy.
Drew -----Original Message----- From: u2-users-boun...@listserver.u2ug.org [mailto:u2-users-boun...@listserver.u2ug.org] On Behalf Of Ed Clark Sent: Friday, January 21, 2011 9:47 AM To: U2 Users List Subject: Re: [U2] 3.99 x 3 = 11 These aren't bugs. They are features :) Going all the way back to the beginnings with pick and microdata/reality, math in the F and A processing codes has been integer only. This was on purpose, for speed I think. And it works fine if you follow the fundamental rule of not using decimal points internally. If you want your users to input 3.99 then your input routine should use ICONV to scale it to 399, and then scale again on output. _______________________________________________ U2-Users mailing list U2-Users@listserver.u2ug.org http://listserver.u2ug.org/mailman/listinfo/u2-users
