1berry/nodejs
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

doc: remove "note that" from events.md

Browse Source 
Refs: https://github.com/nodejs/remark-preset-lint-node/pull/16

PR-URL: https://github.com/nodejs/node/pull/28329
Reviewed-By: Gus Caplan <me@gus.host>
Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>
Reviewed-By: Tobias Nießen <tniessen@tnie.de>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
This commit is contained in:
Rich Trott 2019-06-20 13:54:55 -06:00
parent 2cd4a6f4b4
commit 5faa53789a
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
doc/api/events.md
View File

@ -261,7 +261,7 @@ change affects *all* `EventEmitter` instances, including those created before
the change is made. However, calling [`emitter.setMaxListeners(n)`][] still has the change is made. However, calling [`emitter.setMaxListeners(n)`][] still has
precedence over `EventEmitter.defaultMaxListeners`. precedence over `EventEmitter.defaultMaxListeners`.
Note that this is not a hard limit. The `EventEmitter` instance will allow This is not a hard limit. The `EventEmitter` instance will allow
more listeners to be added but will output a trace warning to stderr indicating more listeners to be added but will output a trace warning to stderr indicating
that a "possible EventEmitter memory leak" has been detected. For any single that a "possible EventEmitter memory leak" has been detected. For any single
`EventEmitter`, the `emitter.getMaxListeners()` and `emitter.setMaxListeners()` `EventEmitter`, the `emitter.getMaxListeners()` and `emitter.setMaxListeners()`
@ -508,7 +508,7 @@ added: v0.1.26
Removes all listeners, or those of the specified `eventName`. Removes all listeners, or those of the specified `eventName`.
Note that it is bad practice to remove listeners added elsewhere in the code, It is bad practice to remove listeners added elsewhere in the code,
particularly when the `EventEmitter` instance was created by some other particularly when the `EventEmitter` instance was created by some other
component or module (e.g. sockets or file streams). component or module (e.g. sockets or file streams).
@ -539,7 +539,7 @@ listener array. If any single listener has been added multiple times to the
listener array for the specified `eventName`, then `removeListener()` must be listener array for the specified `eventName`, then `removeListener()` must be
called multiple times to remove each instance. called multiple times to remove each instance.
Note that once an event has been emitted, all listeners attached to it at the Once an event has been emitted, all listeners attached to it at the
time of emitting will be called in order. This implies that any time of emitting will be called in order. This implies that any
`removeListener()` or `removeAllListeners()` calls *after* emitting and `removeListener()` or `removeAllListeners()` calls *after* emitting and
*before* the last listener finishes execution will not remove them from *before* the last listener finishes execution will not remove them from