mirrors/nodejs
mirrors/nodejs
0
0
Fork 0
mirror of https://github.com/nodejs/node.git synced 2024-12-01 16:10:02 +01:00
Code Issues Releases Activity

doc: fix link to Event Loop page

Browse Source 
PR-URL: https://github.com/nodejs/node/pull/9527
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
This commit is contained in:
timathon 2016-11-09 12:07:49 +08:00 committed by Roman Reiss
parent e12b9bedec
commit 843770406b
No known key found for this signature in database
GPG Key ID: 2E62B41C93869443
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/guides/timers-in-node.md
View File

@ -10,7 +10,7 @@ period of time. Timers do not need to be imported via `require()`, since
all the methods are available globally to emulate the browser JavaScript API.
To fully understand when timer functions will be executed, it's a good idea to
read up on the the Node.js
[Event Loop](../topics/event-loop-timers-and-nexttick).
[Event Loop](../topics/event-loop-timers-and-nexttick.md).
## Controlling the Time Continuum with Node.js
@ -96,7 +96,7 @@ some major ways they differ. The first is that `process.nextTick()` will run
*before* any `Immediate`s that are set as well as before any scheduled I/O.
The second is that `process.nextTick()` is non-clearable, meaning once
code has been scheduled to execute with `process.nextTick()`, the execution
cannot be stopped, just like with a normal function. Refer to [this guide](../topics/event-loop-timers-and-nexttick#processnexttick)
cannot be stopped, just like with a normal function. Refer to [this guide](../topics/event-loop-timers-and-nexttick.md#processnexttick)
to better understand the operation of `process.nextTick()`.
### "Infinite Loop" Execution ~ *`setInterval()`*