Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!cmcl2!kramden.acf.nyu.edu!brnstnd
From: brnstnd@kramden.acf.nyu.edu (Dan Bernstein)
Newsgroups: comp.lang.c
Subject: Re: &&**
Message-ID: <20757:Sep1115:30:0390@kramden.acf.nyu.edu>
Date: 11 Sep 90 15:30:03 GMT
References: <1990Sep7.021321.18381@watmath.waterloo.edu> <1990Sep7.080855.24070@irisa.fr> <0926@sheol.UUCP>
Distribution: usa
Organization: IR
Lines: 10

In article <0926@sheol.UUCP> throopw@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