Path: csiph.com!eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Ben Bacarisse Newsgroups: comp.lang.javascript Subject: Re: Understanding && Date: Fri, 16 Apr 2021 16:09:13 +0100 Organization: A noiseless patient Spider Lines: 16 Message-ID: <87wnt2e06e.fsf@bsb.me.uk> References: Mime-Version: 1.0 Content-Type: text/plain Injection-Info: reader02.eternal-september.org; posting-host="bcf9a544088c93a28385d943b82a88e7"; logging-data="22585"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+6pMlJGKXulrnelcbzViNSr/sTsQQaOj0=" Cancel-Lock: sha1:ZY+FQJdulRRndndnA3QPWrMhbkc= sha1:dSZi0WVTDvYhtdDzm8QSC9lsdnQ= X-BSB-Auth: 1.b086f5e374fedc0dd7ab.20210416160913BST.87wnt2e06e.fsf@bsb.me.uk Xref: csiph.com comp.lang.javascript:39952 Jon Ribbens writes: > You most often see this sort of thing in JavaScript that was > automatically generated by a compiler (either because the original > source was in something else like TypeScript or a more modern version > of JavaScript or because the author wanted to compress/minify the > script), but human beings are also quite capable of writing hard-to-read > code like this. Is that specifically when the right-hand operand is an assignment expression? I don't find that hard to read but then I'm used to assignment being and expression so it seems like a natural extension of the more frequently seen uses of &&. -- Ben.