Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!ncrlnk!ncrcae!hubcap!gatech!ncar!ames!haven!ncifcrf!nlm-mcs!adm!smoke!gwyn
From: gwyn@smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: possible operator precedence bug?
Message-ID: <8680@smoke.ARPA>
Date: 13 Oct 88 08:45:22 GMT
Article-I.D.: smoke.8680
References: <751@mcrware.UUCP> <4700025@m.cs.uiuc.edu>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 14

In article <4700025@m.cs.uiuc.edu> kenny@m.cs.uiuc.edu writes:
-	a ? b , c : d
-has no such problem.  There is no lexical confusion, particularly when
-the spaces that I show are supplied.  There is no ambiguity in the
-parse; the only syntactically correct interpretation is 
-	a ? (b , c) : d .
-Then, as long as c and d are type-compatible, and a can be coerced to
-an integral type, the expression has a meaningful interpretation
-semantically.  (The ice is thin if b and c are type-incompatible --
-does anyone know if the latest dpANS is clearer on this point?)

I don't see the issue.  b,c does not require type compatibility
for b and c.  That comma-expression has the type of c.  Type
compatibility constraints apply after the parse is already done.