Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.javascript > #33440 > unrolled thread
| Started by | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| First post | 2017-05-30 14:34 +0100 |
| Last post | 2017-06-01 00:00 -0700 |
| Articles | 2 on this page of 22 — 5 participants |
Back to article view | Back to comp.lang.javascript
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: x === x Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-30 14:34 +0100
Re: x === x Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-30 15:02 +0100
Re: x === x Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-05-30 16:22 +0200
Re: x === x Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-31 01:02 +0100
Re: x === x Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-05-31 12:39 +0200
Re: x === x Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-05-31 21:52 +0100
Re: x === x Thomas 'PointedEars' Lahn <PointedEars@web.de> - 2017-05-31 23:39 +0200
Re: x === x Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-01 01:46 +0100
Re: x === x Julio Di Egidio <julio@diegidio.name> - 2017-06-01 00:14 -0700
Re: x === x John G Harris <niam@jghnorth.org.uk.invalid> - 2017-06-01 10:39 +0100
Re: x === x Julio Di Egidio <julio@diegidio.name> - 2017-06-01 03:37 -0700
Re: x === x John G Harris <niam@jghnorth.org.uk.invalid> - 2017-06-01 18:54 +0100
Re: x === x Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-01 21:54 +0100
Re: x === x John G Harris <niam@jghnorth.org.uk.invalid> - 2017-06-02 11:06 +0100
Re: x === x John G Harris <niam@jghnorth.org.uk.invalid> - 2017-06-02 11:08 +0100
Re: x === x John G Harris <niam@jghnorth.org.uk.invalid> - 2017-06-02 10:56 +0100
Re: x === x Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-04 12:50 +0100
Re: x === x John G Harris <niam@jghnorth.org.uk.invalid> - 2017-06-04 14:30 +0100
Re: x === x Dr J R Stockton <J.R.Stockton@physics.org> - 2017-06-04 09:03 -0700
Re: x === x Ben Bacarisse <ben.usenet@bsb.me.uk> - 2017-06-01 14:45 +0100
Re: x === x Julio Di Egidio <julio@diegidio.name> - 2017-06-01 07:00 -0700
Re: x === x Julio Di Egidio <julio@diegidio.name> - 2017-06-01 00:00 -0700
Page 2 of 2 — ← Prev page 1 [2]
| From | Julio Di Egidio <julio@diegidio.name> |
|---|---|
| Date | 2017-06-01 07:00 -0700 |
| Message-ID | <13c86ceb-da33-4749-858e-7a6f14c21cf3@googlegroups.com> |
| In reply to | #33473 |
On Thursday, June 1, 2017 at 3:45:37 PM UTC+2, Ben Bacarisse wrote: > That would clarify what you consider to be "the syntax". That is the stupidest thing I have heard this week. > Alternatively you could be rude again, and I'll know not to try to > understand your position. Read my previous reply, if you can read at all: I just won't insist on a disamina of your bullshit and then lies, we should go back to basic English grammar and you'd still be producing fallacies. Get a life... Julio
[toc] | [prev] | [next] | [standalone]
| From | Julio Di Egidio <julio@diegidio.name> |
|---|---|
| Date | 2017-06-01 00:00 -0700 |
| Message-ID | <ac9ce676-f927-44ba-9ee0-3320265caa36@googlegroups.com> |
| In reply to | #33448 |
On Wednesday, 31 May 2017 12:39:57 UTC+2, Thomas 'PointedEars' Lahn wrote:
> Ben Bacarisse wrote:
> > Thomas 'PointedEars' Lahn <PointedEars@web.de> writes:
> >> Stefan Ram wrote:
> >>> Ben Bacarisse <ben.usenet@bsb.me.uk> writes:
> >>>> What's wrong with {} === {}?
> >>> It depends on the context.
It doesn't.
> >> No, it does not. “===” *makes* the (expression) context.
> >
> > $ nodejs -c -e '[] === [];' && echo "ok"
> > ok
> > $ nodejs -c -e '{} === {};' && echo "ok"
> > [eval]:1
> > {} === {};
> > ^^^
> >
> > SyntaxError: Unexpected token ===
> > <snip trace-back>
> > $ nodejs -c -e '({} === {});' && echo "ok" ✘
> > ok
>
> Fascinating. I had tried in the Chrome DevTools Console, and there the
> trailing semicolon makes the difference:
>
> | > {} === {}
> | <- false
> | {} === {};
> | (x) Uncaught SyntaxError: Unexpected token ===
>
> I assume that the explicit semicolon there is considered an /EmptyStatement/
> that switches back to statement context.
There is no empty statement anywhere. The first one is parsed as just an
expression, the second one, due to the semi-colon, must be a statement,
and will fail to parse.
Julio
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | comp.lang.javascript
csiph-web