ObjFW  History of src/OFASPrintF.h of bcff1dfd70c5e7d9

Forgot to add 2017, even though I already did quite some changes in
2017. file: [adfec6bf61] check-in: [44f45c2e35] user: js, branch: trunk, size: 1043 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [ad462d74be] check-in: [cec0f072f8] user: js, branch: 0.8, size: 1049 [annotate] [blame] [check-ins using] [diff]

While at it, also update the mail address. file: [2f198b1fe5] check-in: [2a27cf3000] user: js, branch: trunk, size: 1037 [annotate] [blame] [check-ins using] [diff]

Now that Clang switched to use _Nullable and _Nonnull instead of
__nullable / __nonnull, there is no longer a conflict with glibc, which
means we can just define _Nullable / _Nonnull to nothing if they are not
understood by the compiler (which did not work with __nullable /
__nonnull due to this conflict).

This also defines _Null_unspecified to nothing if unavailable. file: [eedd732e01] check-in: [d526d938d7] user: js, branch: trunk, size: 1033 [annotate] [blame] [check-ins using] [diff]

Using __nonnull directly doesn't work on systems using glibc, as glibc
defines __nonnull as a parameterized define. While this does not fix the
problem of Clang introducing __nonnull even though it conflicts with
glibc, this at least means it's possible again to compile things with
versions of Clang that don't support __nonnull on systems with glibc. file: [7fb013ccb5] check-in: [b7097a67b6] user: js, branch: trunk, size: 1045 [annotate] [blame] [check-ins using] [diff]