|
4 | 4 |
|
5 | 5 | > Stability: 2 - Stable
|
6 | 6 |
|
7 |
| -Prior to the introduction of [`TypedArray`] in ECMAScript 2015 (ES6), the |
| 7 | +Prior to the introduction of [`TypedArray`] in [`ECMAScript 2015`] (ES6), the |
8 | 8 | JavaScript language had no mechanism for reading or manipulating streams
|
9 | 9 | of binary data. The `Buffer` class was introduced as part of the Node.js
|
10 | 10 | API to make it possible to interact with octet streams in the context of things
|
@@ -192,7 +192,7 @@ encoding may incorrectly decode the characters.
|
192 | 192 | ## Buffers and TypedArray
|
193 | 193 |
|
194 | 194 | `Buffer` instances are also [`Uint8Array`] instances. However, there are subtle
|
195 |
| -incompatibilities with the TypedArray specification in ECMAScript 2015. |
| 195 | +incompatibilities with the TypedArray specification in [`ECMAScript 2015`]. |
196 | 196 | For example, while [`ArrayBuffer#slice()`] creates a copy of the slice, the
|
197 | 197 | implementation of [`Buffer#slice()`][`buf.slice()`] creates a view over the
|
198 | 198 | existing `Buffer` without copying, making [`Buffer#slice()`][`buf.slice()`] far
|
@@ -272,7 +272,7 @@ function:
|
272 | 272 |
|
273 | 273 | ## Buffers and ES6 iteration
|
274 | 274 |
|
275 |
| -`Buffer` instances can be iterated over using the ECMAScript 2015 (ES6) `for..of` |
| 275 | +`Buffer` instances can be iterated over using the [`ECMAScript 2015`] (ES6) `for..of` |
276 | 276 | syntax.
|
277 | 277 |
|
278 | 278 | Example:
|
@@ -2553,3 +2553,4 @@ console.log(buf);
|
2553 | 2553 | [`Uint32Array`]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Uint32Array
|
2554 | 2554 | [`Uint8Array`]: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Uint8Array
|
2555 | 2555 | [WHATWG spec]: https://encoding.spec.whatwg.org/
|
| 2556 | +[`ECMAScript 2015`]: https://www.ecma-international.org/ecma-262/6.0/index.html |
0 commit comments