summaryrefslogtreecommitdiff
path: root/shallow.h
diff options
context:
space:
mode:
authorÆvar Arnfjörð Bjarmason <avarab@gmail.com>2021-09-27 12:54:25 (GMT)
committerJunio C Hamano <gitster@pobox.com>2021-09-27 21:47:59 (GMT)
commit9865b6e6a4ca1e895fd473c827cf1822f3bd8249 (patch)
treea042ff50d16f1a328592aa46a11311ab66585077 /shallow.h
parent9d444d9ee019cb795e6a677fbb70daf6ae64a073 (diff)
downloadgit-9865b6e6a4ca1e895fd473c827cf1822f3bd8249.zip
git-9865b6e6a4ca1e895fd473c827cf1822f3bd8249.tar.gz
git-9865b6e6a4ca1e895fd473c827cf1822f3bd8249.tar.bz2
*.[ch] *_INIT macros: use { 0 } for a "zero out" idiom
In C it isn't required to specify that all members of a struct are zero'd out to 0, NULL or '\0', just providing a "{ 0 }" will accomplish that. Let's also change code that provided N zero'd fields to just provide one, and change e.g. "{ NULL }" to "{ 0 }" for consistency. I.e. even if the first member is a pointer let's use "0" instead of "NULL". The point of using "0" consistently is to pick one, and to not have the reader wonder why we're not using the same pattern everywhere. Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'shallow.h')
0 files changed, 0 insertions, 0 deletions