ObjFW  History of src/resolver.h of 7e5c81e18629e9a7

Instead, OFDNSResolver is used for everything now. check-in: [6e9ee122eb] user: js, branch: trunk, size: 0

This replaces of_address_to_string_and_port(). file: [8e4bcb1595] check-in: [8aeee6680a] user: js, branch: trunk, size: 1764 [annotate] [blame] [check-ins using] [diff]

Casts are now written like types in variable declarations. file: [d006d1407a] check-in: [4af49a13c3] user: js, branch: trunk, size: 2400 [annotate] [blame] [check-ins using] [diff]

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

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

While at it, also update the mail address. file: [61e89a3dd8] check-in: [2a27cf3000] user: js, branch: trunk, size: 2389 [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: [5d077f79a9] check-in: [d526d938d7] user: js, branch: trunk, size: 2385 [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: [f92afcb5a7] check-in: [b7097a67b6] user: js, branch: trunk, size: 2399 [annotate] [blame] [check-ins using] [diff]

It is now called +[getHost:andPort:forAddress:]. This makes it much
clearer from the selector alone what it actually does. file: [2d84450251] check-in: [fb590316ba] user: js, branch: trunk, size: 2209 [annotate] [blame] [check-ins using] [diff]

This is in preparation for UDP sockets, so that they can share the
resolving functionality with TCP sockets. file: [5eef0c526a] check-in: [49b1989b63] user: js, branch: trunk, size: 1913 [annotate] [blame] [check-ins using]