Malcolm said -
"It also really matters if you get it wrong ( ! ) as a binary 1 sent
usually does something, and a binary 0 does not."
It certainly does something Malcolm.
I know somebody very well who not so long ago, in a remote process control
context, put a '1' in a macro when he intended it to be '0'.
The result...?
1. A fire an a treatment oven. (No one was harmed - physically)
2. The first blemish on the factory safety record for >18 months.
3. Negative safety-related £bonus in _all_ factory pay packets.
4. [ ] <- insert your own guess at what might be in the
personnel file!
5. A sort of absence from the works canteen for a bit!
All for the want of a '0'.
It's (become) a funny old world.
I liked the copper wire bits - still laaaarrfing.
John in Wales
