3 ms·
I've seen them get quite a bit of use in graphical code, which is, well, actually fairly common in JS. Code that uses bitwise operations looks fairly ugly as i
by yoklov 13y ago
I've seen them get quite a bit of use in graphical code, which is, well, actually fairly common in JS.
Code that uses bitwise operations looks fairly ugly as is. Hav e you considered enabling them with a prefix or suffix? E.G. ^$ instead of bitxor, or >>$ instead of bitrshift...
- cameronkknight 13y agoThat could be possible, you could even do it today, if you wanted: macro operator binary ^$ ASTE $left bitxor $right There are also operators for `and`, `or`, `xor` which act logically. `not` which does a boolean invert. So there are `bitand`, `bitor`, `bitxor`, `bitnot` which fit well as working bitwise instead of logically. I suppose the outliers are `bitlshift`, `bitrshift`, `biturshift`, but it does somewhat make sense to keep the `bit` prefix because it casts to int32 and because its operations are inherently bitwise.