From 8706f2efea7853d1404ab8c1ed5960151bdcda08 Mon Sep 17 00:00:00 2001 From: pansay Date: Tue, 17 Mar 2015 15:18:20 +0100 Subject: [PATCH] Update reassignment.md --- .../markdown/References and Rebinding/reassignment.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/manuscript/markdown/References and Rebinding/reassignment.md b/manuscript/markdown/References and Rebinding/reassignment.md index 07c01a3..1320e18 100644 --- a/manuscript/markdown/References and Rebinding/reassignment.md +++ b/manuscript/markdown/References and Rebinding/reassignment.md @@ -70,8 +70,8 @@ You can do the same thing with both syntaxes for accessing objects: name.middleName = 'Austin' name //=> { firstName: 'Leonard', - # lastName: 'Braithwaite', - # middleName: 'Austin' } + // lastName: 'Braithwaite', + // middleName: 'Austin' } We have established that JavaScript's semantics allow for two different bindings to refer to the same value. For example: @@ -107,4 +107,4 @@ The outer value of `allHallowsEve` was not changed because all we did was rebind This is different. We haven't rebound the inner name to a different variable, we've mutated the value that both bindings share. Now that we've finished with mutation and aliases, let's have a look at it. -T> JavaScript permits the reassignment of new values to existing bindings, as well as the reassignment and assignment of new values to elements of containers such as arrays and objects. Mutating existing objects has special implications when two bindings are aliases of the same value. \ No newline at end of file +T> JavaScript permits the reassignment of new values to existing bindings, as well as the reassignment and assignment of new values to elements of containers such as arrays and objects. Mutating existing objects has special implications when two bindings are aliases of the same value.