&&**

[Dan Bernstein]

In article <0926 at sheol.UUCP> throopw at sheol.UUCP (Wayne Throop) writes:
  [ that if a compiler reduces &&**x to x then it is buggy ]

Question for the standards people: Is && undefined, unspecified,
implementation-defined, or what have you? Unless it's simply erroneous,
compilers that always delete &* or *& are only being efficient, and
Wayne's faith in the competence of compiler designers should remain
firm.

---Dan