Robert Klemme wrote:

> 
> "Henrik Horneber" <ryco / gmx.net> schrieb im Newsbeitrag 
> news:415E787B.7050108 / gmx.net...
> 
>> Well yes, I was aware of that fact, that's why I was using BigDecimals 
>> in the first place. I was _not_ aware of the fact, that
>> - turning a float to a string
>> - turning the string to a BigDecimal
>> - turning the BigDecimal to a float
>> generates such problems, just because strings and BigDecimals seemed a 
>> 'wider' type to me. Now that you mention it, it is kind of obvious 
>> that there still are these problems, because of different 
>> representations. Strange how such perceptions of 'wider' or 'more 
>> precise' can fool you...
> 
> 
> Well, the weakest link in the chain is the crucial one and in this case 
> it's the float.  So as long as the values are converted into a float 
> once somewhere in the process you can bet that == will fail at some 
> point. :-)
> 

This is what it boils down to, agreed. I guess I just can't see the 
forrest because of all those trees.

Henrik