Editing
JavaScript/Notes/Scope
(section)
Jump to navigation
Jump to search
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
== Declaration Binding Instantiation == [http://www.ecma-international.org/ecma-262/5.1/#sec-10.5 § 10.5] Every execution context has an associated VariableEnvironment. Variables and functions declared in ECMAScript code evaluated in an execution context are added as bindings in that VariableEnvironment’s Environment Record. For function code, parameters are also added as bindings to that Environment Record. From [https://groups.google.com/forum/#!topic/jsmentors/JnHM3Pvesp8 global object property access]. <blockquote> Consider the following "weird" behavior with the global object: <source lang="javascript"> console.log(window.foo); // this returns undefined console.log(this.foo); // this returns undefined console.log(foo); // this is a reference error </source> Accessing a non existent property on an object should return undefined... which accounts for the first two cases... but whats going on in the third case? </blockquote> the ECMAScript specification on <code>[http://www.ecma-international.org/ecma-262/5.1/#sec-15.11.6.3 ReferenceError]</code> explains that <code>ReferenceError</code> is also thrown in strict mode when making an assignment to an undeclared identifer. <source lang="javascript"> (function(){ "use strict"; erwt = 1; })(); // ReferenceError </source> Back to the example, getting a property off an object, the prototype chain is searched. When that happens, if the property is not found, then <code>undefined</code> results. But with scope chain resolution, when the property is not resolved, an error results. <blockquote style="white-space:pre"> | 11.1.2 Identifier Reference | An Identifier is evaluated by performing Identifier Resolution | as specified in 10.3.1. The result of evaluating an Identifier | is always a value of type Reference. </blockquote> ... <blockquote style="white-space:pre"> | 10.3.1 Identifier Resolution | Identifier resolution is the process of determining the binding of an | Identifier using the <code>LexicalEnvironment</code> of the running execution context. </blockquote> <blockquote style="white-space:pre"> > console.log(foo); // this is a reference error > </blockquote> <p>Identifier <code>foo</code> is resolved to a Reference with null as the base object. In ES5, it looks as if it is a Reference with base object as <code>undefined</code>. With either spec, the result will be the same: <code>ReferenceError</code>. ES5 gets a little fancy with the explanation. <blockquote style="white-space:pre"> > The Mozilla docs on Reference error simply state: > > A ReferenceError is thrown when trying to dereference a variable that > has not been declared. > </blockquote> They mean that when you try and get the value of an Identifier in a PrimaryExpression and the Identifier is not resolved, then the base object is null (or now <code>undefined</code>) that the attempt to get at the value is going to result in a <code>ReferenceError</code>. So when you have an Expression like: <pre> console.log(foo); </pre> or even just a PrimaryExpression: <pre> foo // a PrimaryExpression. </pre> Identifier <code>foo</code> must be first resolved. The base object for that value is null (or so"undefined") and the when the expression is evaluated, it tries to get the value, and then finds the base object is null and throws a ReferenceError is thrown. | 8.7.1 GetValue (V) | | 1. If Type(V) is not Reference, return V. | 2. Let base be the result of calling GetBase(V). | 3. If IsUnresolvableReference(V), throw a ReferenceError exception. ... | IsUnresolvableReference(V). Returns true if the base value | is undefined and false otherwise. The MDC docs might not say it, and you didn't ask, either, but in strict code, assignment to undeclared Identifier will result in referenceerror too. <blockquote style="white-space:pre"> > I realize accessing a non existent property on an object should return > undefined... which accounts for the first two cases... but whats going > on in the third case? </blockquote> An Identifier resolution was performed on the scope chain. Just remember the difference when getting a property fails: With object properties - the prototype chain is used and the result is undefined. With unqualified Identifiers, the scope chain is searched in the result is ReferenceError.
Summary:
Please note that all contributions to Noisebridge are considered to be released under the Creative Commons Attribution-NonCommercial-ShareAlike (see
Noisebridge:Copyrights
for details). If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here.
You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource.
Do not submit copyrighted work without permission!
To protect the wiki against automated edit spam, we kindly ask you to solve the following CAPTCHA:
Cancel
Editing help
(opens in new window)
Navigation menu
Personal tools
Not logged in
Talk
Contributions
Log in
Request account
Namespaces
Page
Discussion
English
Views
Read
Edit
View history
More
Search
Dig in!
Noisebridge
- Status: MOVED
- Donate
- ABOUT
- Accessibility
- Vision
- Blog
Manual
MANUAL
Visitors
Participation
Community Standards
Channels
Operations
Events
EVENTS
Guilds
GUILDS
- Meta
- Electronics
- Fabrication
- Games
- Music
- Library
- Neuro
- Philosophy
- Funding
- Art
- Crypto
- Documentation/Wiki
Wiki
Recent Changes
Random Page
Help
Categories
(Edit)
Tools
What links here
Related changes
Special pages
Page information