ObjFW  History of src/OFInflateStream.m of 2e9336b1efd820b3

Otherwise we spin forever if the underlying stream keeps returning 0 on
read.

This can happen if the end of a ZIP part has been reached. Returning
allows to switch the underlying stream to the next part. file: [533f2c6519] check-in: [f7faf2bfa6] user: js, branch: 1.0, size: 17142 [annotate] [blame] [check-ins using] [diff]

Otherwise we spin forever if the underlying stream keeps returning 0 on
read.

This can happen if the end of a ZIP part has been reached. Returning
allows to switch the underlying stream to the next part. file: [9d9894c2fe] check-in: [a72f602c2a] user: js, branch: trunk, size: 17121 [annotate] [blame] [check-ins using] [diff]

This allows for a much cleaner solution to avoid the internal read
buffer of e.g. a TLS connection never being processed while waiting for
a delimiter. file: [fd902a590d] check-in: [a61e0594b4] user: js, branch: trunk, size: 17068 [annotate] [blame] [check-ins using] [diff]

This uses the same format as OFEnsure(). file: [a61e69ad62] check-in: [c86b8f10f0] user: js, branch: trunk, size: 17048 [annotate] [blame] [check-ins using] [diff]

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

The new names should be more accurate. file: [95c86a8053] check-in: [627511b032] user: js, branch: trunk, size: 16884 [annotate] [blame] [check-ins using] [diff]

Still miscompiles things. file: [c1d8d6e047] check-in: [9e9ce6aa1c] user: js, branch: trunk, size: 16898 [annotate] [blame] [check-ins using] [diff]

This means refusing to close twice, calling -[close] from -[dealloc] and
not calling -[cancelAsyncRequests].

Calling -[cancelAsyncRequests] in -[close] is too dangerous, as -[close]
gets called by -[dealloc]: If the queue is the last reference to the
object, at the point where -[cancelAsyncRequests] removes it from the
queue, the object will start to deallocate and call into
-[cancelAsyncRequests] again, which is still in the middle of removing
it and now finds itself with an inconsistent state. file: [3cf4fd3893] check-in: [3b43d51006] user: js, branch: trunk, size: 16890 [annotate] [blame] [check-ins using] [diff]

This gives a significant performance improvement, cutting decompression
time almost in half. file: [5b9953e18a] check-in: [6a0bf8be32] user: js, branch: trunk, size: 16815 [annotate] [blame] [check-ins using] [diff]

This includes GCC thinking uint16_t and uint_fast16_t have a different
signedness and pointers to subclasses of OFStream and pointers to
OFStream being incompatible pointer types. file: [cd213df087] check-in: [44413ada84] user: js, branch: trunk, size: 16493 [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: [360414f679] check-in: [2f4e0df8be] user: js, branch: trunk, size: 18798 [annotate] [blame] [check-ins using] [diff]

There is not much point in having a bi-directional stream for Deflate
compression / decompression. file: [f2182fa6d3] check-in: [f56a50ee50] user: js, branch: trunk, size: 18794 [annotate] [blame] [check-ins using]

The reason for renaming to OFInflateStream was to have one stream for
decompression and one for compression in order to reduce memory usage if
only one of the two is needed, as the ivar layout will be smaller then.
However, it is more consistent with other stream classes to have one
stream that can handle both. The increased memory footprint of having
ivars for compression and decompression can be solved by having a
pointer to those instead. This will not incur any performance penalty,
as the pointer will be dereferenced instead of the ivars, meaning the
overhead is only getting the pointer from the ivars once. check-in: [134a1121c7] user: js, branch: trunk, size: 0

(U)INT_FAST*_MAX is broken on Android, which makes (u)int_fast*_t
dangerous to use while it does not provide any real speed benefit. file: [47e2756e95] check-in: [d3158d091f] user: js, branch: trunk, size: 18741 [annotate] [blame] [check-ins using] [diff]

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