- Bit fields (flags)
They’re the most efficient way of representing something whose state is defined by several “yes or no” properties. ACLs are a good example; if you have let’s say 4 discrete permissions (read, write, execute, change policy), it’s better to store this in 1 byte rather than waste 4. These can be mapped to enumeration types in many languages for added convenience.
- Communication over ports/sockets
Always involves checksums, parity, stop bits, flow control algorithms, and so on, which usually depend on the logic values of individual bytes as opposed to numeric values, since the medium may only be capable of transmitting one bit at a time.
- Compression, Encryption
Both of these are heavily dependent on bitwise algorithms. Look at the deflate algorithm for an example – everything is in bits, not bytes.
- Finite State Machines
I’m speaking primarily of the kind embedded in some piece of hardware, although they can be found in software too. These are combinatorial in nature – they might literally be getting “compiled” down to a bunch of logic gates, so they have to be expressed as AND, OR, NOT, etc.
- Graphics There’s hardly enough space here to get into every area where these operators are used in graphics programming.
XOR (or ^) is particularly interesting here because applying the same input a second time will undo the first. Older GUIs used to rely on this for selection highlighting and other overlays, in order to eliminate the need for costly redraws. They’re still useful in slow graphics protocols (i.e. remote desktop).
VietMX Staff asked 3 years ago
