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 upIs impossible or possible (typo?) #629
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
UltCombo
Jul 5, 2016
Contributor
An ECMAScript program (e.g. JavaScript running in the browser or Node.js) does not have introspection into environment records or lexical environments—e.g. user code cannot programmatically tell or modify the bindings that exist in a given environment record, there's no such API for that.
|
An ECMAScript program (e.g. JavaScript running in the browser or Node.js) does not have introspection into environment records or lexical environments—e.g. user code cannot programmatically tell or modify the bindings that exist in a given environment record, there's no such API for that. |
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Show comment
Hide comment
iliakan
commented
Jul 5, 2016
|
Ah, I understand what is meant now. |
iliakan
closed this
Jul 5, 2016
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
iliakan commentedJul 5, 2016
Here, the latest phrase https://tc39.github.io/ecma262/#sec-lexical-environments:
Lexical Environments and Environment Record values are purely specification mechanisms and need not correspond to any specific artefact of an ECMAScript implementation. It is impossible for an ECMAScript program to directly access or manipulate such values.
Shouldn't it end like this?
...It is possible for an ECMAScript program to directly access or manipulate such values.