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

Merge pull request #278 from usernamehw/patch-20

Browse source 
Update article.md
This commit is contained in:
Ilya Kantor 2017-11-01 09:00:15 +03:00 • committed by GitHub
commit a61add9800
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
1-js/06-advanced-functions/03-closure/article.md
View file

@ -296,7 +296,7 @@ let counter2 = makeCounter();
alert( counter1() ); // 0 alert( counter1() ); // 0
alert( counter1() ); // 1 alert( counter1() ); // 1
alert( counter2() ); // 0 (independant) alert( counter2() ); // 0 (independent)
``` ```
@ -423,7 +423,7 @@ For instance, after `if` finishes, the `alert` below won't see the `user`, hence
For a loop, every run has a separate Lexical Environment. If the variable is declared in `for`, then it's also local to that Lexical Environment: For a loop, every run has a separate Lexical Environment. If the variable is declared in `for`, then it's also local to that Lexical Environment:
```js run ```js run
for(let i = 0; i < 10; i++) { for (let i = 0; i < 10; i++) {
// Each loop has its own Lexical Environment // Each loop has its own Lexical Environment
// {i: value} // {i: value}
} }
@ -567,7 +567,7 @@ Lexical Environment objects that we've been talking about are subjects to same m
return function() { alert(value); }; return function() { alert(value); };
} }
// 3 functions in array, every of them links to Lexical Environment // 3 functions in array, every one of them links to Lexical Environment
// from the corresponding f() run // from the corresponding f() run
// LE LE LE // LE LE LE
let arr = [f(), f(), f()]; let arr = [f(), f(), f()];
@ -641,6 +641,6 @@ g();
```warn header="See ya!" ```warn header="See ya!"
This feature of V8 is good to know. If you are debugging with Chrome/Opera, sooner or later you will meet it. This feature of V8 is good to know. If you are debugging with Chrome/Opera, sooner or later you will meet it.
That is not a bug of debugger, but a special feature of V8. Maybe it will be changed some time. That is not a bug of debugger, but a special feature of V8. Maybe it will be changed sometime.
You always can check for it by running examples on this page. You always can check for it by running examples on this page.
``` ```