Goo'day,
As one of the proponents of changing WIDEZERO away from 0x3dc00000 to 0x3eb00000 to alleviate the "this *IS* equal to that" syndrome, I have now been forced to swing away from that "fix" to climbing through the code and doing away with all of the *100 and /100 in favour of I-and OCONVs, and/or INTing the calculation.....
This has been brought home to me quite forcibly by the QM data model... ....
At 11:02 22/11/04 -0700, you wrote:
<snip> The problem turned out to be a loose nut on my keyboard (yes, mine). Remember a thread a while back on the WIDE0 setting in uvconfig? I decided to be pro-active because we do a bunch of precision calculations and what might it hurt to change? It hurts any IF numeric comparison that falls within some parameter for the given array.
<snip>
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.290 / Virus Database: 265.4.1 - Release Date: 19/11/04
-- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.290 / Virus Database: 265.4.1 - Release Date: 19/11/04
Regards,
Bruce Nichol Talon Computer Services ALBURY NSW 2640 Australia
www.taloncs.com.au
Tel: +61 (0)411149636 Fax: +61 (0)260232119
If it ain't broke, fix it till it is!
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.290 / Virus Database: 265.4.1 - Release Date: 19/11/04
-- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.290 / Virus Database: 265.4.1 - Release Date: 19/11/04 ------- u2-users mailing list [EMAIL PROTECTED] To unsubscribe please visit http://listserver.u2ug.org/
