[12:07:30 AM] TW: I am unable to determine how to respond.
[12:08:23 AM] Johnny Danger: at YYG's incompetence right? dude i'm sorry but GMS just cracks me up sometimes... is_bool() returns true for "(1 = 2)" but not for "false"... wtf???
[12:08:51 AM] TW: isn't false actually a range from 0 to .999999~ or something?
[12:09:02 AM] TW: i think it's because YYGs didnt implement true and false as actual boolean values
[12:09:08 AM] TW: 0 and 1 should be the actual ones
[12:09:22 AM] Johnny Danger: nope those don't pass either
[12:09:33 AM] TW: well, i was gonna say, the function doesnt work either way, lol
[12:09:41 AM] Johnny Danger: it's a "special" 0 and 1 I think, if you add 2 + "special 1" it's still 1 for example
[12:09:49 AM] TW: even if those worked, the fact that the others didnt work means it's broken somehow
[12:11:26 AM | Edited 12:12:59 AM] TW: ah, i have a Q, what if you turned down the mathematical precision? to like, no decimal possible # at all... i wonder if true, false, 0, and 1, would all be properly read & write'd then. hmm, oh well, it wouldn't make much sense if it did work / fix it / etc., anyway, so it doesnt matter much.
[12:13:14 AM] Johnny Danger: good idea, but it didn't make a difference - my unit tests all run as they did before