Joyee Cheung 1432065e9d lib: correct error.errno to always be numeric ... Historically `error.errno` of system errors thrown by Node.js can sometimes be the same as `err.code`, which are string representations of the error numbers. This is useless and incorrect, and results in an information loss for users since then they will have to resort to something like `process.binding('uv'[`UV_${errno}`])` to get to the numeric error codes. This patch corrects this behavior by always setting `error.errno` to be negative numbers. For fabricated errors like `ENOTFOUND`, `error.errno` is now undefined since there is no numeric equivalent for them anyway. For c-ares errors, `error.errno` is now undefined because the numeric representations (negated) can be in conflict with libuv error codes - this is fine since numeric codes was not available for c-ares errors anyway. Users can use the public API `util.getSystemErrorName(errno)` to retrieve string codes for these numbers. PR-URL: https://github.com/nodejs/node/pull/28140 Reviewed-By: James M Snell <jasnell@gmail.com> Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Rich Trott <rtrott@gmail.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com>		2019-06-17 10:18:09 +08:00
..
child.js	lib: enforce the use of Object from primordials	2019-04-12 05:38:45 +02:00
master.js	lib: enforce the use of Object from primordials	2019-04-12 05:38:45 +02:00
round_robin_handle.js	lib: correct error.errno to always be numeric	2019-06-17 10:18:09 +08:00
shared_handle.js	lib: use Array#includes instead of Array#indexOf	2019-03-21 21:38:02 +08:00
utils.js
worker.js	lib: enforce the use of Object from primordials	2019-04-12 05:38:45 +02:00