diff options
author | Daniel Mack <github@zonque.org> | 2015-09-10 19:01:25 +0200 |
---|---|---|
committer | Daniel Mack <github@zonque.org> | 2015-09-10 19:01:25 +0200 |
commit | 786c5bf957f8f7b78c7a0999908ff822e712b53e (patch) | |
tree | d330ac099c5d75669ab5d8d21e880bc29521add8 /CODING_STYLE | |
parent | 15af581253a3f25a71d4fa723bf1fdd22f842728 (diff) | |
parent | e11d45682ed0ccdbdfe71a958718c836114a4610 (diff) |
Merge pull request #1242 from poettering/no-off_t
Drop usage of off_t
Diffstat (limited to 'CODING_STYLE')
-rw-r--r-- | CODING_STYLE | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/CODING_STYLE b/CODING_STYLE index f13f9becbc..98d99dcdaa 100644 --- a/CODING_STYLE +++ b/CODING_STYLE @@ -311,3 +311,13 @@ always-true expression for an infinite while() loop is our recommendation is to simply write it without any such expression by using "for (;;)". + +- Never use the "off_t" type, and particularly avoid it in public + APIs. It's really weirdly defined, as it usually is 64bit and we + don't support it any other way, but it could in theory also be + 32bit. Which one it is depends on a compiler switch chosen by the + compiled program, which hence corrupts APIs using it unless they can + also follow the program's choice. Moreover, in systemd we should + parse values the same way on all architectures and cannot expose + off_t values over D-Bus. To avoid any confusion regarding conversion + and ABIs, always use simply uint64_t directly. |