I thought it is a bug, weird one. Thanks for the explanation.

The problem is quite different, 20 and 2000000000000000 are just very different numbers, it is not the same nubmer with a different number of digits after the decimal point .. there is no decimal point :)

double on Win32 is of course 64bit. long double on SGI and on Sun is 128bit. The question is - why does VC++ produce such a weird output? I am not trying to get 128bit number out of Win32 double, I'm just trying to output it with 50 digits after the decimal point. And when I try to do that, I get completely wrong result. Borland C++ and g++ produce correct results on Win32.

=========== #include int main() { double z = 20.0; std::cout<

#include #include void foo { std::hash_map queries; queries.find(std::string()); } produces C:\...\xhash(38): error C2440: 'type cast' : cannot convert from 'const std::string' to 'size_t' error. That looks like a bug to me, since that is a fine C++ code. looking into xhash we see size_t operator()(const _Kty& _Keyval) const { // hash _Keyval to size_t value return ((size_t)_Keyval); } which is at least weird. Any comments?

What do you think about articles that offer source code, which is not free for commertial use? It looks like a free advertizement on CodeProject for me.