glitch in turing?!?! O.o 405 =/= 405

[chopperdudes]

well if you could just copy and paste the following simple code into turing you'd know what i'm talking about... and it's not about data type conflict as i've shown in the last line...

Turing:

var a := 66430125 put "the number is ", a put "" put a, " to the third root is ", a ** (1 / 3) put "" put "round ", a, " to the third root is ", round (a ** (1 / 3)) put "" put "it is ", a ** (1 / 3) = round (a ** (1 / 3)), " that ", a ** (1 / 3), " = ", round (a ** (1 / 3)) put "" put "it is ", 1.0000 = 1, " that 1.0000 = ", 1

any1 know what's going on?!

[andrew.]

This is a wild guess, but I think when you round in Turing, some information about the real number is lost because it's changing types. It's like if in Java you have two strings that have "Hello" in it. But they aren't equal because their locations in memory are pointers to another location where the strings are located. The pointers are different, so then they are not equal. I think if you make string1 = string2 though, they are the same because they have the same pointer to the exact same place in memory. I don't know if I'm explaining it right...actually I don't even know if I'm right.

[DanielG]

I believe it's simply a rounding error, when turing (and most programming languages) calculate sqrt, it's not perfect, so sqrt(25) might be 5.0000001 or 4.999999, which although appearing as 5 (since it only prints so many digits), it doesn't consider it to be