ObjFW  History of src/OFDeflateStream.h of 44f45c2e357301ef

There is not much point in having a bi-directional stream for Deflate
compression / decompression. check-in: [f56a50ee50] user: js, branch: trunk, size: 0

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

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. file: [da155ca87d] check-in: [134a1121c7] user: js, branch: trunk, size: 2902 [annotate] [blame] [check-ins using]

It makes more sense to have one class for inflating and one for
deflating instead of having one that does both, as having one that does
both requires more memory per instance when only inflating or deflating
is used. check-in: [2e9336b1ef] user: js, branch: trunk, size: 0

No compression support yet, only decompression.

Decompression speed is acceptable for productive use, but there is still
a lot of room for optimization as this is a very straightforward
implementation without much optimization. file: [2f21e16d6f] check-in: [d83d3aa719] user: js, branch: trunk, size: 2827 [annotate] [blame] [check-ins using]