noticed a bit-wise OR where it was clearly intended to be a boolean OR
F fredg1 Member Apr 17, 2021 #1 noticed a bit-wise OR where it was clearly intended to be a boolean OR Attachments OR_typo.patch 725 bytes · Views: 4
MCroft Developer Staff member Apr 18, 2021 #2 On boolean values, it's going to be the same, except it has to evaluate both sides, and doesn't shortcut if the first value is true. Which is meaningless since we calculate the booleans before the compare. But clearly not the desired code. r20690
On boolean values, it's going to be the same, except it has to evaluate both sides, and doesn't shortcut if the first value is true. Which is meaningless since we calculate the booleans before the compare. But clearly not the desired code. r20690
