:= Documentation Clarification Topic is solved

[sirksel]

I had an operator precedence question from a student, who was using && and || for flow control (i.e., to short-circuit fail before an assignment statement). This might be common and worth including more explicitly in the documentation of the assignment operator. It's covered by the not language already there, just not explicitly. Proposed new language in red:

"The precedence of the assignment operators is automatically raised when it would avoid a syntax error or provide more intuitive behavior. For example: not x:=y is evaluated as not (x:=y). Also, x==y && z:=1 is evaluated as x==y && (z:=1), which short-circuits when x doesn't equal y. Similarly, ++Var := X is evaluated as ++(Var := X); and Z>0 ? X:=2 : Y:=2 is evaluated as Z>0 ? (X:=2) : (Y:=2)."

[lexikos]

I've moved this from the Bug Reports forum.

[Ragnar]

Thanks for the suggestion. I've added it.