jeena/en.javascript.info
1
0
Fork 0
Code Issues Pull requests Projects Packages Wiki Activity Actions

today’s typos

Browse source
This commit is contained in:
Thierry Parmentelat 2017-05-11 20:41:00 +02:00
parent d184bf8a98
commit 27a491f265
10 changed files with 41 additions and 40 deletions
Download patch file Download diff file Expand all files Collapse all files

6
1-js/06-advanced-functions/04-var/article.md
View file

@ -49,7 +49,7 @@ alert(test); // true, the variable lives after if
If we used `let test` on the 2nd line, then it wouldn't be visible to `alert`. But `var` ignores code blocks, so we've got a global `test`.
The same thing for loops: `var` can not be block or loop-local:
The same thing for loops: `var` cannot be block- or loop-local:
```js
for(var i = 0; i < 10; i++) {
@ -130,7 +130,7 @@ function sayHi() {
People also call such behavior "hoisting" (raising), because all `var` are "hoisted" (raised) to the top of the function.
So in the example above, `if (false)` branch never executes, but that doesn't matter. The `var` inside it is processed in the beginning of the function, so at the moment of `(*)` there variable exists.
So in the example above, `if (false)` branch never executes, but that doesn't matter. The `var` inside it is processed in the beginning of the function, so at the moment of `(*)` the variable exists.
**Declarations are hoisted, but assignments are not.**
@ -153,7 +153,7 @@ The line `var phrase = "Hello"` has two actions in it:
1. Variable declaration `var`
2. Variable assignment `=`.
The declaration is processed at the start of function execution ("hoisted"), but the assignment always works at the place where it is. So the code works essentially like this:
The declaration is processed at the start of function execution ("hoisted"), but the assignment always works at the place where it appears. So the code works essentially like this:
```js run
function sayHi() {