How does variable assignment work in JavaScript?

How does variable assignment work in JavaScript?

So I was playing around the other day just to see exactly how mass assignment works in JavaScript.
First I tried this example in the console:
a = b = {};
a.foo = ‘bar’;
console.log(b.foo);

The result was “bar” being displayed in an alert. That is fair enough, a and b are really just aliases to the same object. Then I thought, how could I make this example simpler.
a = b = ‘foo’;
a = ‘bar’;
console.log(b);

That is pretty much the same thing, isn’t it? Well this time, it returns foo not bar as I would expect from the behaviour of the first example.
Why does this happen?
N.B. This example could be simplified even more with the following code:

a = {};
b = a;
a.foo = ‘bar’;
console.log(b.foo);

a = ‘foo’;
b = a;
a = ‘bar’;
console.log(b);

(I suspect that JavaScript treats primitives such as strings and integers differently to hashes. Hashes return a pointer while “core” primitives return a copy of themselves)

Solutions/Answers:

Solution 1:

In the first example, you are setting a property of an existing object. In the second example, you are assigning a brand new object.

a = b = {};

a and b are now pointers to the same object. So when you do:

a.foo = 'bar';

It sets b.foo as well since a and b point to the same object.

However!

If you do this instead:

a = 'bar';

you are saying that a points to a different object now. This has no effect on what a pointed to before.

In JavaScript, assigning a variable and assigning a property are 2 different operations. It’s best to think of variables as pointers to objects, and when you assign directly to a variable, you are not modifying any objects, merely repointing your variable to a different object.

But assigning a property, like a.foo, will modify the object that a points to. This, of course, also modifies all other references that point to this object simply because they all point to the same object.

Solution 2:

Your question has already been satisfyingly answered by Squeegy – it has nothing to do with objects vs. primitives, but with reassignment of variables vs. setting properties in the same referenced object.

There seems to be a lot of confusion about JavaScript types in the answers and comments, so here’s a small introduction to JavaScript’s type system:

In JavaScript, there are two fundamentally different kinds of values: primitives and objects (and there is no thing like a ‘hash’).

Strings, numbers and booleans as well as null and undefined are primitives, objects are everything which can have properties. Even arrays and functions are regular objects and therefore can hold arbitrary properties. They just differ in the internal [[Class]] property (functions additionally have a property called [[Call]] and [[Construct]], but hey, that’s details).

The reason that primitive values may behave like objects is because of autoboxing, but the primitives themselves can’t hold any properties.

Here is an example:

var a = 'quux';
a.foo = 'bar';
document.writeln(a.foo);

This will output undefined: a holds a primitive value, which gets promoted to an object when assigning the property foo. But this new object is immediately discarded, so the value of foo is lost.

Think of it like this:

var a = 'quux';
new String(a).foo = 'bar'; // we never save this new object anywhere!
document.writeln(new String(a).foo); // a completly new object gets created

Solution 3:

You’re more or less correct except that what you’re referring to as a “hash” is actually just shorthand syntax for an Object.

In the first example, a and b both refer to the same object. In the second example, you change a to refer to something else.

Solution 4:

here is my version of the answer:

obj = {a:"hello",b:"goodbye"}
x = obj
x.a = "bonjour"

// now obj.a is equal to "bonjour"
// because x has the same reference in memory as obj
// but if I write:
x = {}
x.a = obj.a
x.b = obj.b
x.a = "bonjour"

// now x = {a:"bonjour", b:"goodbye"} and obj = {a:"hello", b:"goodbye"}
// because x points to another place in the memory

Solution 5:

You are setting a to point to a new string object, while b keeps pointing to the old string object.

Solution 6:

In the first case you change some property of the object contained in the variable, in the second case you assign a new value to the variable. That are fundamentally different things. The variables a and b are not somehow magically linked by the first assignment, they just contain the same object. That’s also the case in the second example, until you assign a new value to the b variable.