Path: csiph.com!eternal-september.org!feeder.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: Ben Bacarisse <ben.usenet@bsb.me.uk>
Newsgroups: comp.lang.javascript
Subject: Re: x === x
Date: Tue, 30 May 2017 15:02:55 +0100
Organization: A noiseless patient Spider
Lines: 16
Message-ID: <87y3te1lyo.fsf@bsb.me.uk>
References: <JavaScript-20170530123255@ram.dialup.fu-berlin.de> <874lw231ui.fsf@bsb.me.uk> <context-20170530144335@ram.dialup.fu-berlin.de>
Mime-Version: 1.0
Content-Type: text/plain
Injection-Info: mx02.eternal-september.org; posting-host="100ceef5a96f3ad6ffee895ab2330e2d"; logging-data="16000"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX188DPE3YCmUlCyexQUaECtke9q8KMRSvVg="
Cancel-Lock: sha1:S9HhcB6q6Nxrtx8v7AhJ8XfTXdo= sha1:0rMPtE8IDvthxzm3yd9a6DLp8Ow=
X-BSB-Auth: 1.f4e04bb7dc75b4561b69.20170530150255BST.87y3te1lyo.fsf@bsb.me.uk
Xref: csiph.com comp.lang.javascript:33443

ram@zedat.fu-berlin.de (Stefan Ram) writes:

> Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
>>What's wrong with {} === {}?
>
>   It depends on the context.
>
>   In a context, where a statement can begin, an opening
>   brace might be deemed to be the start of a block.

Oh, I see.  I though you meant they were required (your use of "needs"
suggested that that's what you meant).

<snip>
-- 
Ben.