From mboxrd@z Thu Jan 1 00:00:00 1970 From: Harry Kalogirou Subject: Re: Ambiguities Date: 22 Apr 2002 00:21:09 +0300 Sender: linux-8086-owner@vger.kernel.org Message-ID: <1019424067.495.27.camel@cool> References: Mime-Version: 1.0 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: In-Reply-To: List-Id: Content-Type: text/plain; charset="iso-8859-7" To: Riley Williams Cc: Linux-8086 =D4=E7=ED =CA=F5=F1, 21-04-2002 =F3=F4=E9=F2 22:50, =EF/=E7 Riley Willi= ams =DD=E3=F1=E1=F8=E5: > Hi Harry. >=20 > > I noticed in the CHANGELOG that you resolved some ambiguities in th= e > > source. As far as I know X =3D* Y doen't mean X =3D X * Y, that is = X *=3D > > Y. I wonder what are you trying to say? >=20 > The problem here is an old one - the original K&R C specification > allowed the operation assignment combinations to be specified either > way round, so the sequences *=3D and =3D* *CAN* be regarded as the sa= me. > The same is also true of the other operators. I hit this problem at > university back in 1996, as the standard C compiler on one of the > systems was an old compiler that actually implemented that behaviour, > and the standard compilers on the other machines were newer ones that > didn't implement it. >=20 > Most current C compilers do not implement that aspect of K&R and, as = far > as I know, bcc is amongst the ones that didn't. However, when indent > pointed them out to me, I felt that the safest solution was to simply > get rid of the ambiguities in the first place, so I went through the > code and did just that. The sequence I used was to do `make dup` to > create a test copy of the source, then do `make indent` on the test > copy to locate the occurrances, and finally to edit the original copy > and insert the spaces needed to remove the ambiguities. >=20 > Best wishes from Riley. >=20 Very interesting _feature_... I wonder what was they thinking!!? Harry - To unsubscribe from this list: send the line "unsubscribe linux-8086" i= n the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html