BSD C compiler bug

[Doug Gwyn]

In article <10747 at mimsy.UUCP> chris at mimsy.UUCP (Chris Torek) writes:
-In article <570 at mtxinu.UUCP> tim at mtxinu.UUCP (Tim Wood) writes:
->	unsigned char	**foo;
->	foo = (NULL, NULL);
->	foo = ( !foo ? NULL : (fn(2), NULL) );
-The 11 Jan 1988 draft of the dpANS has this to say about constant
-expressions (p. 56):
...
-That disallows the second expression (foo = (NULL, NULL)) explicitly,
...

What do constant expressions have to do with it?  If this were a
static initializer I could see the relevance, but it's not.  The
reported behavior is simply a bug.