A mirror of https://github.com/madler/zlib.git https://git.lua4.win/zlib/atom?h=v1.2.5.2 2011-12-18T18:39:45+00:00 2011-12-18T18:39:45+00:00 Mark Adler madler@alumni.caltech.edu 2011-12-18T18:39:45+00:00 urn:sha1:fe61dfb8a27754137c2f6a1ff59b1e55d615210e 2011-12-17T22:28:33+00:00 Mark Adler madler@alumni.caltech.edu 2011-12-17T22:28:33+00:00 urn:sha1:4ab814df83f0ef5a0ccb28f19c3bd52c837ae4ec 2011-12-14T12:21:00+00:00 Mark Adler madler@alumni.caltech.edu 2011-12-14T12:21:00+00:00 urn:sha1:2556706d67b471b45e0882ea4f32aa8b2efc14ec Also since gzread() will no longer return an error for an incomplete gzip file, have gzclose() return an error if the last gzread() ended in the middle of a gzip stream. 2011-12-14T06:29:37+00:00 Mark Adler madler@alumni.caltech.edu 2011-12-14T06:25:59+00:00 urn:sha1:850a198ff1879e506c961c91da30009539ed14b3 Z_BUF_ERROR was also being used for an unsuccessful gzungetc and for buffer lengths that didn't fit in an int. Those uses were changed to Z_DATA_ERROR in order to assure that Z_BUF_ERROR occurs only when a premature end of input occurs, indicating that gzclearerr() can be used. 2011-12-12T07:30:56+00:00 Mark Adler madler@alumni.caltech.edu 2011-12-12T07:30:56+00:00 urn:sha1:377173b57ef9fab5066481a87a1901bd72fa2c32 2011-12-12T02:22:04+00:00 Mark Adler madler@alumni.caltech.edu 2011-10-13T06:24:31+00:00 urn:sha1:98f5779f4257682ba9b5fc490557618e3f15f84b Before, gzeof() would return true (accurately) when the last read request went just up to the end of the uncompressed data. In the analogous case, feof() would return false, only returning true when a read request goes past the end of the file. This patch corrects gzeof() to behave in the same way as feof(), as noted in the zlib.h documentation. 2011-12-11T06:33:24+00:00 Mark Adler madler@alumni.caltech.edu 2011-12-11T06:27:24+00:00 urn:sha1:70e3b1ca56f2ffe8944d3ac0d59b8781127bf94f 2011-12-11T06:33:24+00:00 Mark Adler madler@alumni.caltech.edu 2011-12-09T03:03:56+00:00 urn:sha1:421c7a61f08ff255bf898f0e687b7d7c8fbdae77 inflate() avoided that allocation normally, until it was modified to update the window on a normal completion so that inflateResetKeep() could work. This patch restores that behavior, but only when Z_FINISH is used successfully to complete an inflation of a stream in a single call of inflate(). The comments in zlib.h have been updated accordingly. 2011-12-11T06:33:17+00:00 Mark Adler madler@alumni.caltech.edu 2011-12-08T18:16:31+00:00 urn:sha1:fb00fda903bbd128952a8ecac4b4f6b459245012 gzwrite.c had hard-coded parameters to deflateInit2() which could contradict compile-time options for the use of less memory and fewer code bits. This patch suggested by Karsten Saunte fixes that. 2011-12-08T08:13:52+00:00 Mark Adler madler@alumni.caltech.edu 2011-12-08T07:57:37+00:00 urn:sha1:afe7cf78d51b819dcdc5b0f4cb85a25a52a9fcd0 This patch adds the deflateResetKeep() function to retain the sliding window for the next deflate operation, and fixes an inflateResetKeep() problem that came from inflate() not updating the window when the stream completed. This enables constructing and decompressing a series of concatenated deflate streams where each can depend on the history of uncompressed data that precedes it. This generalizes deflateSetDictionary() and inflateSetDictionary() to permit setting the dictionary in the middle of a stream for raw deflate and inflate. This in combination with the Keep functions enables a scheme for updating files block by block with the transmission of compressed data, where blocks are sent with deflateResetKeep() to retain history for better compression, and deflateSetDictionary() is used for blocks already present at the receiver to skip compression but insert that data in the history, again for better compression. The corresponding inflate calls are done on the receiver side.