From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: References: From: minux Date: Fri, 5 Dec 2014 01:49:44 -0500 Message-ID: To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: multipart/alternative; boundary=001a11c221088e4d740509727c0e Subject: Re: [9fans] Is the go9p project still maintained? Topicbox-Message-UUID: 33d2ee60-ead9-11e9-9d60-3106f5b1d025 --001a11c221088e4d740509727c0e Content-Type: text/plain; charset=UTF-8 On Fri, Dec 5, 2014 at 12:53 AM, wrote: > > which also contains a suggested patch > > Did you check that the proposed patch actually works? > > I see no difference between: > > a || b > and > a || (a && b) which is (a || a) && (a || b) > a || (a && b) is actually just a fancier way to write a. if a is true, the result is true, if a is false, the result will be a && b, however, as a is already false, it's false. in go9p.patch, the suggested change is actually from a || b to a || (b && a), this is slightly different. But it's still just a fancier way to write a. --001a11c221088e4d740509727c0e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Fri, Dec 5, 2014 at 12:53 AM, <lucio@proxima.alt.za> = wrote:
> which also c= ontains a suggested patch

Did you check that the proposed patch actually works?

I see no difference between:

=C2=A0 =C2=A0 =C2=A0 =C2=A0 a || b
and
=C2=A0 =C2=A0 =C2=A0 =C2=A0 a || (a && b) which is (a || a) &&a= mp; (a || b)
a || (a && b) is actually just a = fancier way to write a.

if a is true, the result i= s true,
if a is false, the result will be a && b, however= , as a is already false, it's false.

in go9p.p= atch, the suggested change is actually from a || b to a || (b && a)= ,
this is slightly different. But it's still just a fancier w= ay to write a.
--001a11c221088e4d740509727c0e--