> On the other hand, the assignment of NaN to a double depends on the fcr. > (And on my machine, curiously changes 0x7ff0...1 to 0x7ff8...1).
http://en.wikipedia.org/wiki/NaN explains the difference between a signaling nan and a quiet nan (the latter). > So if I think of enum definitions as assignment, it makes sense, mostly. how does a non-constant enum make sense? more to the point, in porting code, you're going to have to work out how to deal with NaNs. plan 9 defaults to using signaling nans, unless you manually change the fcr. this is good because it avoids bad conversions. on the other hand, your application may require and depend on the ability to pass around nan and ±inf. - erik
