Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upContradiction concerning Execution Contexts? #980
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
bterlson
Aug 29, 2017
Member
Yeah I think that statement is misleading. I'll probably just remove it.
|
Yeah I think that statement is misleading. I'll probably just remove it. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
tmerr
Aug 30, 2017
Contributor
As far as I can tell the statement was accurate back in 5.1 then broke in 6.0. Removal would be great!
|
As far as I can tell the statement was accurate back in 5.1 then broke in 6.0. Removal would be great! |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
|
@tmerr want to send a PR? |
added a commit
to tmerr/ecma262
that referenced
this issue
Aug 30, 2017
tmerr
referenced this issue
Aug 30, 2017
Merged
Editorial: Remove out-of-date sentence about execution contexts #986
bterlson
closed this
in
#986
Aug 31, 2017
added a commit
that referenced
this issue
Aug 31, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
tmerr commentedAug 21, 2017
Section
8.3 Execution Contextsclaims:Is this always the case?
With the program
var x = 3; eval("let y = 4");,directwould be true, andstrictwould be false. So upon entering the eval we would create an Execution Context with an empty LexicalEnvironmnent (aside from itsouter), and reuse the old VariableEnvironment. Doesn't this contradict the claim that "When an execution context is created its LexicalEnvironment and VariableEnvironment components initially have the same value"?