Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.
Name:
Email:
Subject:
Message icon:
Verification:
Type the letters shown in the picture
Listen to the letters / Request another image

Type the letters shown in the picture:
What color is grass?:
What is the seventh word in this sentence?:
What is five minus two (use the full word)?:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Wisp
« on: August 29, 2009, 05:54:31 PM »

Yes, I just consulted the readme (after posting, of course) and saw the difference between | and |=.
No, I'll never learn.
Thanks anyway.
Posted by: devSin
« on: August 29, 2009, 05:49:44 PM »

EQUALS is assignment in this case.

The first is correct (if lower_bound > 20; gitc=0 else gitc=gitc|2).

The second is incorrect (you're basically saying "else gitc=gitc=gitc|2").
Posted by: Wisp
« on: August 29, 2009, 05:40:53 PM »

This works:
Code: [Select]
gitc_flags = gitc_lower_bound > 20 ? 0 : gitc_flags BOR 2

This gives an OR_EQUALS parse error:
Code: [Select]
gitc_flags = gitc_lower_bound > 20 ? 0 : gitc_flags |= 2

The other *_EQUALS appears to be likewise affected (but I only tested BAND/&= and +=).