Lines Matching refs:on

73 - `else` blocks should generally start on the same line as the closing `}`:
149 - Do not write functions that clobber call-by-reference variables on
151   variables only on success. The rule is: never clobber return parameters on
152   failure, always initialize return parameters on success.
174   much. systemd-internal headers must not rely on an include order, so it is
200 - Our focus is on the GNU libc (glibc), not any other libcs. If other libcs are
201   incompatible with glibc it's on them. However, if there are equivalent POSIX
261 - Instead of using `memzero()`/`memset()` to initialize structs allocated on
334   some exceptions: for constructors, it is OK to return `NULL` on OOM. For
341 - libc system calls typically return -1 on error (with the error code in
342   `errno`), and >= 0 on success. Use the RET_NERRNO() helper if you are looking
413   a "non-logging" function. "Logging" functions do (non-debug) logging on their
414   own, "non-logging" functions never log on their own (except at debug level)
449   `alloca_safe()` or VLAs. If you do allocate fixed-size strings on the stack,
486   the parent much, much later on.
496   broken on Linux).
498 - When applying C-style unescaping as well as specifier expansion on the same
507 - Make sure to enforce limits on every user controllable resource. If the user
522   types based on `short`. They *never* make sense. Use `int`, `long`, `long
525   and so on, as well as `size_t`, but nothing else. Do not use kernel types
526   like `u32` and so on, leave that to the kernel.
533   other way, but it could in theory also be 32-bit. Which one it is depends on
536   systemd we should parse values the same way on all architectures and cannot
542   benefit, and on calls like `printf()` `float`s get promoted to `double`s
570   - `F_DUPFD_CLOEXEC` should be used instead of `F_DUPFD`, and so on,
576   file system objects. This is a good idea so that we don't end up blocking on
580   effect on the regular file. If in doubt consider turning off `O_NONBLOCK`
592   - Do not print full `help()` on error, be specific about the error.
593   - Do not print messages to stdout on error.
612   useful for client applications. Hence, please be careful and avoid `const` on
643   really is happening, after all `htonl()` and `htons()` don't operate on
644   `long`s and `short`s as their name would suggest, but on `uint32_t` and
649   two reasons: first, you want `O_CLOEXEC` set on the new `fd` (see
674   on Linux. Note that `NAME_MAX` does not include space for a trailing `NUL`,
680   name of some kind. For example "journal: ", "nspawn: " and so on.