Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Ben Bacarisse Newsgroups: comp.lang.javascript Subject: Re: x === x Date: Wed, 31 May 2017 01:02:08 +0100 Organization: A noiseless patient Spider Lines: 25 Message-ID: <87inkh28sf.fsf@bsb.me.uk> References: <874lw231ui.fsf@bsb.me.uk> <2872662.aeNJFYEL58@PointedEars.de> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: mx02.eternal-september.org; posting-host="04e45becd6848d7651d9f559a5a1bcb5"; logging-data="23335"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+RfDJgdcKjsdTpoBfMottV6HzcqWSyWe0=" Cancel-Lock: sha1:NIVxTdVb4Fgi50fDRtTPiKWZbXc= sha1:yqBgIhTfao+domEDCbsL+KE8Sac= X-BSB-Auth: 1.4570642f7ab29b4fadfc.20170531010208BST.87inkh28sf.fsf@bsb.me.uk Xref: csiph.com comp.lang.javascript:33447 Thomas 'PointedEars' Lahn writes: > Stefan Ram wrote: > >> Ben Bacarisse writes: >>> What's wrong with {} === {}? >> >> It depends on the context. > > No, it does not. “===” *makes* the (expression) context. $ nodejs -c -e '[] === [];' && echo "ok" ok $ nodejs -c -e '{} === {};' && echo "ok" [eval]:1 {} === {}; ^^^ SyntaxError: Unexpected token === $ nodejs -c -e '({} === {});' && echo "ok" ✘ ok -- Ben.