&&**
Dan Bernstein
brnstnd at kramden.acf.nyu.edu
Wed Sep 12 01:30:03 AEST 1990
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
More information about the Comp.lang.c
mailing list