git-ashish · April 29, 2017 09:47 · Jan 8, 2015 · Jan 8, 2015 · Jan 8, 2015 · Jan 8, 2015
diff --git a/m.js b/m.js
@@ -0,0 +1,8 @@
+// M
+
+var x = (function sayHi() {
+  console.log('hi!')
+})
+
+x() // works
+sayHi() // does not work
diff --git a/0.md b/0.md
@@ -19,6 +19,6 @@ This behavior is called 'hoisting' because it is almost like the function defini
 
 Assignments are not evaluated until the code is executed. An example of an assignment is `var foo = function() {}` or `var foo = function foo() {}`. A function must not be associated with an assignment in order for it to be hoisted (see example `L`)
 
-Wrapping a function in parenthesis (`()`) is a quick way to create a new scope. I personally do not use this pattern regularly as I find it overly confusing to newbies etc, but I have included it because it is widely used in e.g. jQuery plugins.
+Wrapping a function in parenthesis (`()`) is a quick way to convert a function definition into a function expression, which means it does not get hoisted (similar to assigning the function to a variable). I personally do not use this pattern regularly as I find it overly confusing to newbies etc, but I have included it because it is widely used in e.g. jQuery plugins.
 
 I use hoisting as a code organization tool, for example [here](https://github.com/maxogden/dat/blob/4cb75247f181bb1d9a8d312d0d2ff5462d8d2698/lib/write-stream.js#L17) I rely on hoisting to make `parseStream()` available on line 20, even though it is defined on line 41, which I think makes that file more readable as I can put the 'meat' of the function at the top.
diff --git a/0.md b/0.md
@@ -15,7 +15,7 @@ A crude timeline of how JS gets executed:
 1. Parse the scope and detect all function definitions
 2. Execute the code top-to-bottom with all functions found in step 1 available as variables
 
-This behavior is called 'hoisting' because it is almost like the function definitions has been 'hoisted' up to the top of the function.
+This behavior is called 'hoisting' because it is almost like the function definitions have been 'hoisted' up to the top of the function.
 
 Assignments are not evaluated until the code is executed. An example of an assignment is `var foo = function() {}` or `var foo = function foo() {}`. A function must not be associated with an assignment in order for it to be hoisted (see example `L`)
 

diff --git a/0.md b/0.md
@@ -2,7 +2,7 @@
 
 Below are many examples of function hoisting behavior in JavaScript. Ones marked as `works` successfuly print 'hi!' without errors.
 
-To play around with these examples (recommended) save them as e.g. `a.js` on your computer and execute them with `node a.js`
+To play around with these examples (recommended) clone them with git and execute them with e.g. `node a.js`
 
 ### Notes on hoisting
 

diff --git a/0.md b/0.md
@@ -1,6 +1,6 @@
 # JavaScript function hoisting by example
 
-Below are many examples of hoisting behavior in JavaScript. Ones marked as working successfuly print 'hi!' without errors.
+Below are many examples of function hoisting behavior in JavaScript. Ones marked as `works` successfuly print 'hi!' without errors.
 
 To play around with these examples (recommended) save them as e.g. `a.js` on your computer and execute them with `node a.js`
 
@@ -19,4 +19,6 @@ This behavior is called 'hoisting' because it is almost like the function defini
 
 Assignments are not evaluated until the code is executed. An example of an assignment is `var foo = function() {}` or `var foo = function foo() {}`. A function must not be associated with an assignment in order for it to be hoisted (see example `L`)
 
-Wrapping a function in parenthesis (`()`) is a quick way to create a new scope. I personally do not use this pattern regularly as I find it overly confusing to newbies etc, but I have included it because it is widely used in e.g. jQuery plugins.
+Wrapping a function in parenthesis (`()`) is a quick way to create a new scope. I personally do not use this pattern regularly as I find it overly confusing to newbies etc, but I have included it because it is widely used in e.g. jQuery plugins.
+
+I use hoisting as a code organization tool, for example [here](https://github.com/maxogden/dat/blob/4cb75247f181bb1d9a8d312d0d2ff5462d8d2698/lib/write-stream.js#L17) I rely on hoisting to make `parseStream()` available on line 20, even though it is defined on line 41, which I think makes that file more readable as I can put the 'meat' of the function at the top.
diff --git a/0.md b/0.md
@@ -1,4 +1,4 @@
-# Hoisting by example
+# JavaScript function hoisting by example
 
 Below are many examples of hoisting behavior in JavaScript. Ones marked as working successfuly print 'hi!' without errors.
 

diff --git a/0.md b/0.md
@@ -2,7 +2,7 @@
 
 Below are many examples of hoisting behavior in JavaScript. Ones marked as working successfuly print 'hi!' without errors.
 
-The recommended way to run these if you want to play around (recommended) is to save them as e.g. `a.js` on your computer and execute them with `node a.js`
+To play around with these examples (recommended) save them as e.g. `a.js` on your computer and execute them with `node a.js`
 
 ### Notes on hoisting
 

diff --git a/0.md b/0.md
@@ -6,7 +6,7 @@ The recommended way to run these if you want to play around (recommended) is to
 
 ### Notes on hoisting
 
-**(I may be using incorrect terms below, please forgive me)**
+*(I may be using incorrect terms below, please forgive me)*
 
 When JS is parsed, a first pass is done over each scope, and function definitions are immediately discovered. An example of a function definition is `function foo() {}`. When a function is declared like this, with a name, that name becomes available to the entire scope when the code in that scope is executed.
 

diff --git a/0.md b/0.md
@@ -0,0 +1,22 @@
+# Hoisting by example
+
+Below are many examples of hoisting behavior in JavaScript. Ones marked as working successfuly print 'hi!' without errors.
+
+The recommended way to run these if you want to play around (recommended) is to save them as e.g. `a.js` on your computer and execute them with `node a.js`
+
+### Notes on hoisting
+
+**(I may be using incorrect terms below, please forgive me)**
+
+When JS is parsed, a first pass is done over each scope, and function definitions are immediately discovered. An example of a function definition is `function foo() {}`. When a function is declared like this, with a name, that name becomes available to the entire scope when the code in that scope is executed.
+
+A crude timeline of how JS gets executed:
+
+1. Parse the scope and detect all function definitions
+2. Execute the code top-to-bottom with all functions found in step 1 available as variables
+
+This behavior is called 'hoisting' because it is almost like the function definitions has been 'hoisted' up to the top of the function.
+
+Assignments are not evaluated until the code is executed. An example of an assignment is `var foo = function() {}` or `var foo = function foo() {}`. A function must not be associated with an assignment in order for it to be hoisted (see example `L`)
+
+Wrapping a function in parenthesis (`()`) is a quick way to create a new scope. I personally do not use this pattern regularly as I find it overly confusing to newbies etc, but I have included it because it is widely used in e.g. jQuery plugins.
diff --git a/a.js b/a.js
@@ -4,4 +4,4 @@ function sayHi() {
   console.log('hi!')
 }
 
-sayHi()
+sayHi()
diff --git a/l.js b/l.js
@@ -0,0 +1,7 @@
+// L (does not work)
+
+sayHi()
+
+var x = function sayHi() {
+  console.log('hi!')
+}
diff --git a/a.js b/a.js
@@ -0,0 +1,7 @@
+// A (works)
+
+function sayHi() {
+  console.log('hi!')
+}
+
+sayHi()
diff --git a/b.js b/b.js
@@ -0,0 +1,7 @@
+// B (works)
+
+sayHi()
+
+function sayHi() {
+  console.log('hi!')
+}
diff --git a/c.js b/c.js
@@ -0,0 +1,7 @@
+// C (works)
+
+var sayHi = function() {
+  console.log('hi!')
+}
+
+sayHi()
diff --git a/d.js b/d.js
@@ -0,0 +1,7 @@
+// D (does not work)
+
+sayHi()  
+
+var sayHi = function() {
+  console.log('hi!')
+}
diff --git a/e.js b/e.js
@@ -0,0 +1,7 @@
+// E (does not work)
+
+(function sayHi() {
+  console.log('hi!')
+})
+
+sayHi()
diff --git a/f.js b/f.js
@@ -0,0 +1,7 @@
+// F (does not work)
+
+sayHi()
+
+(function sayHi() {
+  console.log('hi!')
+})
diff --git a/g.js b/g.js
@@ -0,0 +1,5 @@
+// G (works)
+
+(function sayHi() {
+  console.log('hi!')
+})()
diff --git a/h.js b/h.js
@@ -0,0 +1,5 @@
+// H (works)
+
+(function() {
+  console.log('hi!')
+})()
diff --git a/i.js b/i.js
@@ -0,0 +1,5 @@
+// I (works)
+
+var sayHi = (function() {
+  console.log('hi!')
+})()
diff --git a/index.js b/index.js
@@ -1,88 +0,0 @@
-// JS hoisting by example
-// Do you fully understand each one?
-
-// A (works)
-
-function sayHi() {
-  console.log('hi!')
-}
-
-sayHi()
-
-// B (works)
-
-sayHi()
-
-function sayHi() {
-  console.log('hi!')
-}
-
-// C (works)
-
-var sayHi = function() {
-  console.log('hi!')
-}
-
-sayHi()  
-
-// D (does not work)
-
-sayHi()  
-
-var sayHi = function() {
-  console.log('hi!')
-}
-
-// E (does not work)
-
-(function sayHi() {
-  console.log('hi!')
-})
-
-sayHi()
-
-// F (does not work)
-
-sayHi()
-
-(function sayHi() {
-  console.log('hi!')
-})
-
-// G (works)
-
-(function sayHi() {
-  console.log('hi!')
-})()
-
-// H (works)
-
-(function() {
-  console.log('hi!')
-})()
-
-// I (works)
-
-var sayHi = (function() {
-  console.log('hi!')
-})()
-
-// J (works)
-
-var sayHi = (function() {
-  console.log('hi!')
-})
-
-sayHi()
-
-// K (does not work) 
-
-sayHi()
-
-var sayHi = (function() {
-  console.log('hi!')
-})
-
-// editors note: because I write JS without semicolons I would
-// never actually begin lines with ( in actual code
-

diff --git a/j.js b/j.js
@@ -0,0 +1,7 @@
+// J (works)
+
+var sayHi = (function() {
+  console.log('hi!')
+})
+
+sayHi()
diff --git a/k.js b/k.js
@@ -0,0 +1,7 @@
+// K (does not work) 
+
+sayHi()
+
+var sayHi = (function() {
+  console.log('hi!')
+})
diff --git a/index.js b/index.js
@@ -0,0 +1,88 @@
+// JS hoisting by example
+// Do you fully understand each one?
+
+// A (works)
+
+function sayHi() {
+  console.log('hi!')
+}
+
+sayHi()
+
+// B (works)
+
+sayHi()
+
+function sayHi() {
+  console.log('hi!')
+}
+
+// C (works)
+
+var sayHi = function() {
+  console.log('hi!')
+}
+
+sayHi()  
+
+// D (does not work)
+
+sayHi()  
+
+var sayHi = function() {
+  console.log('hi!')
+}
+
+// E (does not work)
+
+(function sayHi() {
+  console.log('hi!')
+})
+
+sayHi()
+
+// F (does not work)
+
+sayHi()
+
+(function sayHi() {
+  console.log('hi!')
+})
+
+// G (works)
+
+(function sayHi() {
+  console.log('hi!')
+})()
+
+// H (works)
+
+(function() {
+  console.log('hi!')
+})()
+
+// I (works)
+
+var sayHi = (function() {
+  console.log('hi!')
+})()
+
+// J (works)
+
+var sayHi = (function() {
+  console.log('hi!')
+})
+
+sayHi()
+
+// K (does not work) 
+
+sayHi()
+
+var sayHi = (function() {
+  console.log('hi!')
+})
+
+// editors note: because I write JS without semicolons I would
+// never actually begin lines with ( in actual code
+
No results found