Lines Matching defs:zfree
101 free_func zfree; /* used to free the internal state */
102 voidpf opaque; /* private data object passed to zalloc and zfree */
138 to zero. The application must initialize zalloc, zfree and opaque before
143 parameter for calls of zalloc and zfree. This can be useful for custom
148 If zlib is used in a multi-threaded application, zalloc and zfree must be
149 thread safe. In that case, zlib is thread-safe. When zalloc and zfree are
153 On 16-bit systems, the functions zalloc and zfree must be able to allocate
214 #define Z_NULL 0 /* for initializing zalloc, zfree, opaque */
233 zalloc, zfree and opaque must be initialized before by the caller. If
234 zalloc and zfree are set to Z_NULL, deflateInit updates them to use default
383 next_in, avail_in, zalloc, zfree and opaque must be initialized before by
387 first call). If zalloc and zfree are set to Z_NULL, inflateInit updates
549 fields zalloc, zfree and opaque must be initialized before by the caller.
840 fields next_in, avail_in, zalloc, zfree and opaque must be initialized
1082 calls. The fields zalloc, zfree and opaque in strm must be initialized
1083 before the call. If zalloc and zfree are Z_NULL, then the default library-