CODING_STYLE: say that inet_ntop() is a no no

This commit is contained in:
Zbigniew Jędrzejewski-Szmek 2022-06-04 20:56:29 +02:00
parent 071e522eec
commit a5b28b7721

View File

@ -645,6 +645,11 @@ SPDX-License-Identifier: LGPL-2.1-or-later
`uint16_t`. Also, "network byte order" is just a weird name for "big endian",
hence we might want to call it "big endian" right-away.
- Use `typesafe_inet_ntop()`, `typesafe_inet_ntop4()`, and
`typesafe_inet_ntop6()` instead of `inet_ntop()`. But better yet, use the
`IN_ADDR_TO_STRING()`, `IN4_ADDR_TO_STRING()`, and `IN6_ADDR_TO_STRING()`
macros which allocate an anynomous buffer internally.
- Please never use `dup()`. Use `fcntl(fd, F_DUPFD_CLOEXEC, 3)` instead. For
two reasons: first, you want `O_CLOEXEC` set on the new `fd` (see
above). Second, `dup()` will happily duplicate your `fd` as 0, 1, 2,