b e a r d
@BlinkRape because it is borderline incomprehensible until you know the answer
@beardalaxy @BlinkRape It just depends on paradigm and definition of = as either comparison or variable assignment operator. Within the imperative, and = being an assignment, it would be 30 after evaluation is complete. Within the functional, and = being the comparison, the result of expression would be false and x will remain 23.
@iamtakingiteasy @beardalaxy I don't care one way or the other, the answer is 30 and any other way of doing shit that implies otherwise is wrong and was invented by a retard.
it's also a stupid problem made by someone who thought they were being clever. The answer will always be 30, because in any other space, the statement itself would be illegal as written
it's also a stupid problem made by someone who thought they were being clever. The answer will always be 30, because in any other space, the statement itself would be illegal as written
Follow
@BlinkRape @iamtakingiteasy @beardalaxy
30 = 30+7?
nah, I don't think so. That problem is simply invalid.
The first part has one solution of x=23, but the 2nd half has no possible solutions.
@LukeAlmighty @beardalaxy @iamtakingiteasy computer programmers solved this stupidity a long time ago when they started writing languages that had distinctive functions for comparison operators
No, the answer is 30. I shouldn't even have to explain this.
x is declared to be an initial value of 23
"x = x +7" is adding 7 to the value of X
23 + 7 = 30
that's all there is to it.
The "trick" is that in some fields, the second part is a comparison test and should return a true or false result. But it's intellectual jewry and just meant to fuck with the average person who does not use that nomenclature when doing everyday math, so that is why it is invalid anywhere outside of the academic setting it originated from.