> > *) Change where NaN is generated. Using 0.0/0.0 doesn't > work in VC++ > > because it detects it as a divide-by-zero at the compile stage. > > If they're going to be that anally uncooperative, why don't > they have the required-by-C99-spec macro for NAN? Or at > least some well-defined way to generate a NaN?
They do have one way that's documented on MSDN, which is: unsigned long nan[2]={0xffffffff, 0x7fffffff}; double g = *( double* )nan; I thought that was even uglier ;-), but I can change it to use that on win32 if you prefer it? //Magnus ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly