Lua lied to me :(

[LuaWeaver]

Well, this happened.

Code: Select all

for i=1,nil do end

That errors, of course:
>'for' limit must be a number

So I go and do this:

Code: Select all

for i=1,0/0 do end

That doesn't error! Now, go:

Code: Select all

print(0/0) --> -nan

nan is not a number, so why is for letting me use it as a limit?

[slime]

nan is not a number, so why is for letting me use it as a limit?

Ah, but it is!

Code: Select all

print(type(0/0))

http://en.wikipedia.org/wiki/NaN#Encoding

[raidho36]

Reminds me of:
> issue #666: LÖVE crashes when I try to crash it.

[T-Bone]

I've never thought of this before. It's kind of like Wine except even more obvious

[Xgoff]

ieee probably should have called it something else, like "not representable" or something

reminds me of a past thread on the lua mailing list where someone suggested lua expressions that would have resulted in nan should return nil instead, because "not a number". NOPE.