1. 06 Apr, 2015 2 commits
  2. 25 Mar, 2013 1 commit
  3. 24 Mar, 2013 1 commit
  4. 13 Aug, 2012 1 commit
    • Mark Adler's avatar
      Clean up the usage of z_const and respect const usage within zlib. · 62d6112a
      Mark Adler authored
      This patch allows zlib to compile cleanly with the -Wcast-qual gcc
      warning enabled, but only if ZLIB_CONST is defined, which adds
      const to next_in and msg in z_stream and in the in_func prototype.
      A --const option is added to ./configure which adds -DZLIB_CONST
      to the compile flags, and adds -Wcast-qual to the compile flags
      when ZLIBGCCWARN is set in the environment.
  5. 23 May, 2012 1 commit
  6. 03 May, 2012 1 commit
    • Mark Adler's avatar
      Replace use of unsafe string functions with snprintf if available. · c58f7ab2
      Mark Adler authored
      This avoids warnings in OpenBSD that apparently can't be turned
      off whenever you link strcpy, strcat, or sprintf.  When snprintf
      isn't available, the use of the "unsafe" string functions has
      always in fact been safe, since the lengths are all checked before
      those functions are called.
      We do not use strlcpy or strlcat, since they are not (yet) found on
      all systems.  snprintf on the other hand is part of the C standard
      library and is very common.
  7. 18 Mar, 2012 4 commits
  8. 17 Mar, 2012 1 commit
  9. 11 Mar, 2012 1 commit
  10. 10 Mar, 2012 1 commit
  11. 04 Mar, 2012 1 commit
  12. 03 Mar, 2012 1 commit
  13. 19 Dec, 2011 1 commit
  14. 12 Dec, 2011 1 commit
    • Mark Adler's avatar
      Fix gzeof() to behave just like feof() when read is not past end of file. · 98f5779f
      Mark Adler authored
      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.
  15. 02 Oct, 2011 1 commit
  16. 01 Oct, 2011 2 commits
  17. 27 Sep, 2011 3 commits
  18. 26 Sep, 2011 1 commit
    • Mark Adler's avatar
      Allow gzread() and related to continue after gzclearerr(). · 5ad116ab
      Mark Adler authored
      Before this fix, gzread() would lose data if a premature end of file
      was encountered.  This prevented gzread() from being used on a file
      that was being written concurrently.  Now gzread() returns all of the
      data it has available before indicating a premature end of file.
      This also changes the error returned on a premature end of file from
      Z_DATA_ERROR to Z_BUF_ERROR.  This allows the user to determine if
      the error is recoverable, which it is if Z_BUF_ERROR is returned.  If
      a Z_DATA_ERROR is returned, then the error is not recoverable.
      This patch replaces the functionality of a previous patch that fixed
      reading through an empty gzip stream in a concatenation of gzip
      To implement this fix, a noticeable rewrite of gzread.c was needed.
      The patch has the added advantage of using inflate's gzip processing
      instead of replicating the functionality in gzread.c.  This makes the
      gz code a little simpler.
  19. 11 Sep, 2011 1 commit
  20. 10 Sep, 2011 10 commits