>How are you going to represent 0.3 using a non fixed point integer? I won't try to. The alternative to your proposal is fixed point integer. >if you do, use

>How are you going to represent 0.3 using a non fixed point integer? I won't try to. The alternative to your proposal is fixed point integer. >if you do, use fixed point, you suddenly have other just as common numbers you cant represent.. You really think NaN is a better is a less intuitive result than what whatint64(1)/int64(0) gives? I think it's less of a problem than float. Most programmers (myself included) don't understand all the nuances of floating point. >gettimeofday is deprecated as of 2008 The reason I mentioned it is because I recall it turned out to be a problem when porting/emulating Linux apps under Windows, since the equivalent Windows call used to be way more expensive. Apparently it was a significant problem since the call was in wide use. I don't recall any widespread effort to remove gettimeofday (or equivalents), so I suspect it's still is in use? >With float128 as a core language feature as it should be Unfortunately it isn't a core language feature - e.g. it can have 80bit precision on some x86s/software combinations. Now, that's worth fixing regardless.