>We've increased the precision to 15 significant digits to maintain
>compatibility with Visual Basic, as they also display up to 15 digits of
>precision when using Str. Sorry that this was not documented anywhere, but
>we'll definitely update our docs to reflect this change.
@William, thank you for the explanation.
We appreciate if these kind of (significant) changes are documented
in a release... then we wouldn't need to find out only when we notice
a different behavior and could find the required changes more quickly.
@Norman
>If you care about how a value is presented you should use format, not STR.
Even if we care about the format in the described case, we can't use
'Format'... that's because: "Format will use the information based on the
user's locale"
So depending on the OS set up for Switzerland, Germany, Austria, ... the
reference-files would contain 1,234.45 / 1'234.45 / 1'234,45 ;-)
For us, 'Format' is the way for information shown to the user, but not
for the way it is saved (in a [text]file) for cross-country purpose.
Fortunately we already wrote a Method which does the formatting, so
we only needed to change the Str() to something else (which is a bit
more complicated now)
Juerg
______________________________________
Roth Soft
Kellhofstrasse
CH-8476 Stammheim
E-Mail: juerg.raess@lehreroffice.ch
Internet: http://www.lehreroffice.ch
______________________________________
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|