ObjFW  History of src/OFZIPArchiveEntry.h of f6cc2092af2a9dd2

Also makes OF(Mutable){LHA,Tar,ZIP}ArchiveEntry conform to it, providing
a common protocol to access archives. file: [920d757f40] check-in: [a325d5a1ee] user: js, branch: trunk, size: 7563 [annotate] [blame] [check-ins using] [diff]

This is for consistency with OFTarArchiveEntry and OFLHAArchiveEntry. file: [1aff4ade49] check-in: [94c326ab78] user: js, branch: trunk, size: 7879 [annotate] [blame] [check-ins using] [diff]

With TYPEDEF_HIDES_STRUCT set, Doxygen properly handles anonymous
structs and enums that are typedef'd. file: [e18b985df3] check-in: [2fcf5a3052] user: js, branch: trunk, size: 8365 [annotate] [blame] [check-ins using] [diff]

__COUNTER__ does not exist in GCC 4.2, and Apple GCC 4.2 is still the
newest compiler available for macOS 10.5. file: [c6256ab290] check-in: [ef614a225d] user: js, branch: trunk, size: 8126 [annotate] [blame] [check-ins using] [diff]

This allows ABI stability with the fragile ABI. file: [e9ac584951] check-in: [496695d778] user: js, branch: trunk, size: 8104 [annotate] [blame] [check-ins using] [diff]

Instead, explicitly declare them, as OF_ASSUME_NONNULL_{BEGIN,END} does
not apply to implicit return types. This means that after this commit,
all init methods have a nonnull return type, as they should have. file: [9d05415775] check-in: [2f4e0df8be] user: js, branch: trunk, size: 7060 [annotate] [blame] [check-ins using] [diff]

Treating the ZIP64 extra field as part of the entry itself makes things
a lot easier when (re)writing the central directory. file: [ce0ccead6f] check-in: [8ebf6ed443] user: js, branch: trunk, size: 7012 [annotate] [blame] [check-ins using] [diff]

This is in preparation for OFZIPArchive write support. file: [3cb34f0e06] check-in: [1aea73d8b1] user: js, branch: trunk, size: 7011 [annotate] [blame] [check-ins using] [diff]

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

This changes retaining behavior, meaning properties are not returned
retained and autoreleased anymore, so a property returned from a getter
now needs to be manually retained and autoreleased before calling the
setter. However, this is rarely the case and not using atomic improves
performance. file: [51727c4cd0] check-in: [0a73af49f0] user: js, branch: trunk, size: 6293 [annotate] [blame] [check-ins using] [diff]

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

This existed before, but was private.

Additionally, ofzip -lvvv now also shows the general purpose bit flag. file: [9a4ea2bd46] check-in: [41e83e895c] user: js, branch: trunk, size: 6278 [annotate] [blame] [check-ins using] [diff]

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

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

This increases the required GCC version from 4.0 to 4.6 (exception:
Apple GCC, which already supports this with >= 4.0 starting with OS X
10.5). Since even GCC 4.6 is really old by now, there is no point in
still supporting something even older and making the code ugly because
of that. While some hardware and OS support was dropped from GCC 4.6
compared to GCC 4.0, there is nothing in there that would be an
interesting target with the exception of BeOS maybe - but a port to BeOS
can also be achieved using the Haiku support. The other dropped OSes are
mostly old versions of OSes while newer ones are still being supported
(and those newer versions of those OSes still support the same
hardware). file: [91d72f60e8] check-in: [48980f2297] user: js, branch: trunk, size: 6121 [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: [c2340c1919] check-in: [d526d938d7] user: js, branch: trunk, size: 7009 [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: [c1f79ae163] check-in: [b7097a67b6] user: js, branch: trunk, size: 7013 [annotate] [blame] [check-ins using] [diff]

This belongs to OFZIPArchiveEntry. Consequently, it has been renamed to
of_zip_archive_entry_find_extra_field() and made public, so that it can
be used by applications that got the extra field from the
OFZIPArchiveEntry. file: [5c2f6096e1] check-in: [adf754d5fc] user: js, branch: trunk, size: 3086 [annotate] [blame] [check-ins using] [diff]