Path: utzoo!mnetor!uunet!husc6!necntc!ima!haddock!karl
From: karl@haddock.ISC.COM (Karl Heuer)
Newsgroups: comp.lang.c
Subject: Re: ambiguous why?
Message-ID: <3364@haddock.ISC.COM>
Date: 7 Apr 88 15:35:47 GMT
References: <1303@PT.CS.CMU.EDU> <3326@haddock.ISC.COM> <1325@PT.CS.CMU.EDU>
Reply-To: karl@haddock.ima.isc.com (Karl Heuer)
Organization: Interactive Systems, Boston
Lines: 14

In article <1325@PT.CS.CMU.EDU> edw@IUS1.CS.CMU.EDU (Eddie Wyatt) writes:
>>>	warning ambiguous assigment: assignment op taken  [*a+=*b;]
>>Your compiler scans "+=" as two tokens rather than one.  (Fixed in dpANS.)
>>This makes the anachronism "=*" (fixed in dpANS) visible.
>
>What a f***ing hack =* is then!!!!   If *= consists of two tokens
>so should =* which obviously doesn't

As I said, "fixed in dpANS".  The former by insisting that "+=" is one token;
the latter by removing the anachronism.  (The stupid thing has been obsolete
for about 10 years, and there are *still* compilers out there that assume you
must have meant the compound assignment operator!)

Karl W. Z. Heuer (ima!haddock!karl or karl@haddock.isc.com), The Walking Lint