Javascript variable initialization and declaration order

Question

Playing with typescript, I found that when I use array destructuring, it generates some unusual code where variable initialization precedes its declaration, i.e. in following example console shows "undefined"

(function () {
    var _a = 1;
    _c = _a;
    var _c;
})();
console.log(_c);

> ReferenceError: _c is not defined

Why variable _c does not became global?

See "hoisting" stackoverflow.com/questions/7506844/…

elclanrs
– elclanrs

2015-05-13 09:33:12 +00:00
Commented May 13, 2015 at 9:33 — elclanrs
– elclanrs, Commented May 13, 2015 at 9:33

jfriend00 · Accepted Answer · 2015-05-13 09:43:21Z

2

In Javascript, all variable declarations are hoisted to the top of the scope in which they are declared before any code is actually run. So your code example:

(function () {
    var _a = 1;
    _c = _a;
    var _c;
})();
console.log(_c);

Is evaluated like this:

(function () {
    var _a;
    var _c;
    _a = 1;
    _c = _a;
})();
console.log(_c);

Thus, _c is declared locally before it is actually referenced or used and thus it is not an implicit global because it is declared within the scope in which it is referenced and the hoisting ensures it is declared at the beginning of that scope, no matter where the var _c; declaration is within the scope.

Here are some references on the hoisting concept:

JavaScript Scoping and Hoisting

MDN - var statement

Demystifying JavaScript Variable Scope and Hoisting

JavaScript Hoisting Explained

edited May 13, 2015 at 9:43

answered May 13, 2015 at 9:37

jfriend00

711k104 gold badges1.1k silver badges1k bronze badges

Sign up to request clarification or add additional context in comments.

6 Comments

Somescout Over a year ago

Thanks for detailed explanation. But it's really strange language concept.

jfriend00 Over a year ago

@Somescout - it's not strange at all. The parse step gathers all the variable and function declarations for a scope before the code is executed. That works just like compiled languages. Javascript just doesn't force you to place all the definitions at the top of their scope.

Somescout Over a year ago

By "strange" I mean that behavior of preceding code can be changed by latter lines. It is almost always unexpected. (But of course, declaring and relying on global variables inside function is a bad practice itself).

jfriend00 Over a year ago

@Somescout - It's only unexpected if you don't know that Javascript collects all declarations within a scope at parse time and they are available anywhere in the scope. Once you know that, it doesn't seem strange. What I think is "strange" is that use of an undeclared variable is ever allowed. Thank goodness for strict mode which makes that an error.

Somescout Over a year ago

I'd rather disagree (I know and understand hoisting now, but it still seems very strange language design to me), but it's going offtop on top speed.

|

Vinayak · Accepted Answer · 2015-05-13 09:32:51Z

0

All variables under functions are Local variables.

answered May 13, 2015 at 9:32

Vinayak

4233 silver badges22 bronze badges

Collectives™ on Stack Overflow

Javascript variable initialization and declaration order

2 Answers 2

6 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

6 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related