Main index | Section 3 | 日本語 | Options |
Compression can be done in a single step if the buffers are large enough or can be done by repeated calls of the compression function. In the latter case, the application must provide more input and/or consume the output (providing more output space) before each call.
The library also supports reading and writing files in gzip(1) (.gz) format with an interface similar to that of stdio.
The library does not install any signal handler. The decoder checks the consistency of the compressed data, so the library should never crash even in the case of corrupted input.
All functions of the compression library are documented in the file zlib.h. The distribution source includes examples of use of the library in the files test/example.c and test/minigzip.c, as well as other examples in the examples/ directory.
Changes to this version are documented in the file ChangeLog that accompanies the source.
zlib is built in to many languages and operating systems, including but not limited to Java, Python, .NET, PHP, Perl, Ruby, Swift, and Go.
An experimental package to read and write files in the .zip format, written on top of zlib by Gilles Vollant (info@winimage.com), is available at:
http://www.winimage.com/zLibDll/minizip.html and also in the contrib/minizip directory of the main zlib source distribution. | |
http://zlib.net/ | |
The data format used by the zlib library is described by RFC (Request for Comments) 1950 to 1952 in the files: | |
http://tools.ietf.org/html/rfc1950 (for the zlib header and trailer format)
http://tools.ietf.org/html/rfc1951 (for the deflate compressed data format) http://tools.ietf.org/html/rfc1952 (for the gzip header and trailer format) | |
Mark Nelson wrote an article about zlib for the Jan. 1997 issue of Dr. Dobb's Journal; a copy of the article is available at: | |
http://marknelson.us/1997/01/01/zlib-engine/ | |
http://zlib.net/zlib_faq.html | |
Copyright (C) 1995-2022 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this software.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the following restrictions:
0step]. | The origin of this software must not be misrepresented; you must not claim that you wrote the original software. If you use this software in a product, an acknowledgment in the product documentation would be appreciated but is not required. |
0[step]. | Altered source versions must be plainly marked as such, and must not be misrepresented as being the original software. |
0[step]. | This notice may not be removed or altered from any source distribution. |
27 Mar 2022 | ZLIB (3) |
Main index | Section 3 | 日本語 | Options |
Please direct any comments about this manual page service to Ben Bullock. Privacy policy.
“ | C isn't that hard: void (*(*f[])())() defines f as an array of unspecified size, of pointers to functions that return pointers to functions that return void | ” |