Thanks Kay for your detailed answer and everyone who chimed in afterwards..... will have to read it all a couple of times.... ..... i definitely have to do some tests in this regard and see how many decimal points i really need......., but I'm not surprised that the answer is not straight forward ..... lol...... i wish i could explain the use case better, but i have some way to go before i can explain it . seems like lots of workarounds available, so i think the coast is clear.
On Fri, Jul 20, 2018 at 9:32 PM, Bob Sneidar via use-livecode < use-livecode@lists.runrev.com> wrote: > Wouldn't it be great if we could forgo the speed in lieu of accuracy? I > mean, how could you develop an accounting application you could trust with > this caveat? > > Bob S > > > > On Jul 20, 2018, at 17:17 , Kay C Lan via use-livecode < > use-livecode@lists.runrev.com> wrote: > > > > Surprised that no one has replied to this so I'll just offer a bit of > > advice. Whilst on the surface your assumption is correct, 64bit will > > allow more accuracy than 32 bit, what you need to be aware of is the > > same gotchas still apply to 64 bit LC as 32 bit LC. Try this in the > > msg box: > > > > put 283.67-150.00-133.67 > > > > you should get 0. Now try this in the msg box: > > > > put 283.67-150.00-133.67=0 > > > > You will get 'false' when you know you wanted true; whether in 32bit > > or 64 bit LC (Python, JBScript and some other languages) in some cases > > you don't get the answer you know is correct. > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
