Re: Different behavior of Str(Double)? / Re: Floating point overflow

[David Grogono <dave@grogware.com>]

On Sep 29, 2008, at 9:27 AM, Joe Strout wrote:

> > yes: because with 15 significant digits, the double gets  
> > represented more accurate in a string? (-> feature)
> That's what you want, you could use the Variant->String conversion,

Except that as I reported last week, the precision of  
Variant.StringValue has been decreased by 2 digits.  Code that worked  
in earlier versions is now broken in 2008r4.  Here's a simplified  
example:
 dim v as Variant = 1/3
 if val(v.StringValue) = v.DoubleValue then
   MsgBox "Good"
 else
   MsgBox "Bad"
 end

There have obviously been some changes in 2008r4 with Str and  
Variant.StringValue although nothing is mentioned in the release  
notes.  This is what I've seen mentioned so far:
1) Str(1/0) now hangs the app
2) Str has now has 15 digits precision rather than 7
3) Variant.StringValue now has 15 digits precision rather than 17

Obviously the first change was unintentional. Since there are no  
release notes, it is difficult to know whether the other 2 changes  
were intentional but both obviously have the potential to break  
people's code.
- David

--
David Grogono
www.grogware.com




_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>

Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>