Origineel geplaatst door Shabazza:

"x = 0 and (y == 0 or y == 1)"
"x = 1 and (y == 0 or y == 1)"

"=" is assignment.
"==" is comparison.

Each function has it's own scope so xPos and yPos in prepare are not the same variables as xPos and yPos in updatePosition. They are local variables that only exist inside that def block.

Origineel geplaatst door umop-apisdn:

Origineel geplaatst door Shabazza:

"x = 0 and (y == 0 or y == 1)"
"x = 1 and (y == 0 or y == 1)"

"=" is assignment.
"==" is comparison.

That was just me being not precise when writing the post.

Origineel geplaatst door Timon:

Each function has it's own scope so xPos and yPos in prepare are not the same variables as xPos and yPos in updatePosition. They are local variables that only exist inside that def block.

Right.. next question: Does the game "pass by reference" ?
Can I pass the xPos, yPos to my updatePosition and update those variables, or will it again create new instances?
Then I guess I have to use a global dictionary for the position...which I have not unlocked yet.
The game says, dicts are using references. Hm. Hm.
I was just trying to keep calls at a minimum.
Therefore, I fetch those values once, if possible at the highest possible scope.
Old habit of an embedded developer...

Assuming it's running python under the hood and not just emulating the syntax it's pass by object reference. So if it's a mutable object like a list or dict it will be updated because it's the same object you are pointing to. If it's immutable like an integer or string, changing the value will assign a new object and the reference outside of your function will still point to the old object and will not change.

Seems to work as expected.


This code outputs:
old string
[1,2,3]