undefined | Better HN

0 pointsahoge10y ago0 comments

That's from IEEE 754 (a standard for floating-point arithmetic). `NaN` and -0 exist for the same reason.

0 comments

To be fair, just because something is a standard doesn't mean it isn't a dumb implementation. Just by testing the programming languages on my computer, I can tell you that Python, C, and D all throw errors rather than allow it, which is the smart thing to do.

magicalist10y ago

> I can tell you that Python, C, and D all throw errors rather than allow it

Python throws an error, but numpy.divide(1., 0) will work just fine (and return inf).

I'm not sure why you're saying C throws an error. The behavior of dividing by 0 is undefined by default, but on most machines these days the hardware implements IEE-754 and the C implementation will advertise as implementing IEC 60559, so 1. / 0 will give you inf as well.

bionsuba10y ago

Trying to compile a test program with Clang threw errors, and bringing up numpy is disingenuous.

1 more reply

serve_yay10y ago

I know, I was just joshing! Man, you guys really didn't like that one. Personally I enjoy taking a moment now and then to reflect on some of the sillier aspects of JS. This is because I love JS, not because I hate it.

j / k navigate · click thread line to collapse

0 comments

bionsuba10y ago

magicalist10y ago

> I can tell you that Python, C, and D all throw errors rather than allow it

Python throws an error, but numpy.divide(1., 0) will work just fine (and return inf).

bionsuba10y ago

Trying to compile a test program with Clang threw errors, and bringing up numpy is disingenuous.

1 more reply

serve_yay10y ago

j / k navigate · click thread line to collapse