Phil Scadden wrote:[color=blue]
> Thank you Victor. Changing the open statement does work. In my
> defense, I will say that is code is being ported onto Windows, and in
> its original platform, the manual say "b" mean binary but is
> unnecessary. Oddly, it works for 99% of floating point values - well
> to be precise it got the number wrong twice in run over 89000 values.
> This bug report came down from detailed investigation of those two
> strange value that did not match other original from other systems
> nor from gcc on windows.[/color]
Actually, it'll have problems for any values that have the byte 0x0d in
their binary representation. - overall, something on the order of 1 in 50
double values should have problems.
[color=blue]
>[color=green]
>>
http://lab.msdn.microsoft.com/productfeedback/[/color]
>
> Thank you very much for that link. I did not find this from the MS
> support site. In fact the MS New Zealand site does not have a product
> support link for C++ .NET 2003, only 2002 or VS 2003 (which does not
> accept the C++ standard product id). Phone support did not point to
> this link either.[/color]
VS 2003 is C++ .NET 2003 (or rather, a superset of it).
[color=blue]
>
> However, the error is mine in the code and I am extremely
> appreciative of the help that given. My response on Microsoft support
> was surly for which I apologise but offer the above frustrating
> experience in mitigation.
>
> Thanks again, one and all.[/color]
-cd