On May 30, 2012, at 10:25 AM, Tim Mooney wrote:
>> …..
>
> It seems that the integer to double conversion really is not exact for 1.
That seems like a pretty huge flaw in the architecture! I've never encountered a machine with arithmetic that bad!
I suspect the problem is somewhere else. Could it be that the bi record is accepting any non-zero value as 'true' -- so that when read as an integer the value is not '1' as the code expects?
> If so, it wouldn't be exact for either 1.
> Could you try "nint(a)=nint(1)?1:0"
>
--
Eric Norum
[email protected]
- Replies:
- Re: calc VAL field not updating from bi VAL field Maren Purves
- References:
- Re: calc VAL field not updating from bi VAL field Tim Mooney
- Navigate by Date:
- Prev:
Re: Proposed change in asyn - request for comments Eric Norum
- Next:
RE: Proposed change in asyn - request for comments Allison, Stephanie
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: calc VAL field not updating from bi VAL field J. Lewis Muir
- Next:
Re: calc VAL field not updating from bi VAL field Maren Purves
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
<2012>
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·