Speculation!
If you have spaces around them, then:
a /\ b ===> a / b
a \/ b ===> a / b
Logic: the preprocessing phase has to deal with backslash and a character after, and is quite likely to treat backslash-space as space, and backslash-slash as slash.
That said, both the SUN C compiler (version 12) and GNU C compiler (version 4.4) reject code containing the backslash. But I could easily believe that old, pre-standard C preprocessors were less careful about it.
Standards compliance
The operators have never been part of an official version of C.
Also, the standard would not allow the interpretation I gave (section 5.1.1.2 Translation phases, in both C89 and C99) - but non-standard compilers are not constrained by the standard, of course.
Added after the source was posted:
Interesting! So it looks plausible for 'a = b /\ c;
' to assign the maxiumum of b and c to a, and 'a = b \/ c;
' to do the minimum (or, as Greg Hewgill pointed out, more likely vice versa). And, in those days, it was probable that the modern '+=
' operators were still written as '=+
' and were in fact two tokens (no supporting evidence for this assertion; failing memory again), so the hypothetical 'a =/\ b;
' (or, in modern notation, 'a /\= b;
') would have been the max-assignment operator, etc.
It also occurs to me that Thompson's ACM Turing Award speech 'Reflections On Trusting Trust' is somehow relevant.