Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!gem.mps.ohio-state.edu!apple!usc!bloom-beacon!mintaka!think!kulla!barmar
From: barmar@kulla (Barry Margolin)
Newsgroups: comp.lang.c
Subject: Re: C history question
Keywords: C design, XOR
Message-ID: <30291@news.Think.COM>
Date: 28 Sep 89 16:11:09 GMT
References: <10390@phoenix.Princeton.EDU> <29557@news.Think.COM> <883@friar-taac.UUCP> <596@crdos1.crd.ge.COM>
Sender: news@Think.COM
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 15

In article <596@crdos1.crd.ge.COM> davidsen@crdos1.UUCP (bill davidsen) writes:
>In article <29557@news.Think.COM> barmar@think.COM (Barry Margolin) writes:
>|	allok = allok && a[i++] > b[j++]
>|then the side effects on i and j would be different from
>|	allok &= a[i++] > b[j++]
>  What are you saying here? The & and && operators work diferently. 

It started with someone asking why there are no &&= or ||= operators
in C.  Someone suggested that &= could be used whenever you would have
wanted to use &&=.  My posting shows that they are different,
precisely because & and && are different.
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar