From cb5021ae4db09c9bc400e8a3dd07731fa6efa09c Mon Sep 17 00:00:00 2001 From: Nick Pierson Date: Sun, 14 Feb 2016 16:55:43 -0600 Subject: [PATCH] fix grammar in "this & object prototypes" chap. 4 --- this & object prototypes/ch4.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/this & object prototypes/ch4.md b/this & object prototypes/ch4.md index de0b3bd91..6b1a1460a 100644 --- a/this & object prototypes/ch4.md +++ b/this & object prototypes/ch4.md @@ -238,7 +238,7 @@ JavaScript is simpler: it does not provide a native mechanism for "multiple inhe ## Mixins -JavaScript's object mechanism does not *automatically* perform copy behavior when you "inherit" or "instantiate". Plainly, there's no "classes" in JavaScript to instantiate, only objects. And objects don't get copied to other objects, they get *linked together* (more on that in Chapter 5). +JavaScript's object mechanism does not *automatically* perform copy behavior when you "inherit" or "instantiate". Plainly, there are no "classes" in JavaScript to instantiate, only objects. And objects don't get copied to other objects, they get *linked together* (more on that in Chapter 5). Since observed class behaviors in other languages imply copies, let's examine how JS developers **fake** the *missing* copy behavior of classes in JavaScript: mixins. We'll look at two types of "mixin": **explicit** and **implicit**.