Lines Matching refs:zalloc
97 alloc_func zalloc; /* used to allocate the internal state */
99 voidpf opaque; /* private data object passed to zalloc and zfree */
134 to zero. The application must initialize zalloc, zfree and opaque before
139 parameter for calls of zalloc and zfree. This can be useful for custom
143 zalloc must return Z_NULL if there is not enough memory for the object.
144 If zlib is used in a multi-threaded application, zalloc and zfree must be
147 On 16-bit systems, the functions zalloc and zfree must be able to allocate
150 returned by zalloc for objects of exactly 65536 bytes *must* have their
208 #define Z_NULL 0 /* for initializing zalloc, zfree, opaque */
227 zalloc, zfree and opaque must be initialized before by the caller. If
228 zalloc and zfree are set to Z_NULL, deflateInit updates them to use default
371 next_in, avail_in, zalloc, zfree and opaque must be initialized before by
376 inflate. If zalloc and zfree are set to Z_NULL, inflateInit updates them to
535 fields next_in, zalloc, zfree and opaque must be initialized before by the
645 (such as zalloc being Z_NULL). msg is left unchanged in both source and
657 stream state was inconsistent (such as zalloc or state being Z_NULL).
774 fields next_in, avail_in, zalloc, zfree and opaque must be initialized
873 (such as zalloc being Z_NULL). msg is left unchanged in both source and
884 stream state was inconsistent (such as zalloc or state being Z_NULL).
895 stream state was inconsistent (such as zalloc or state being Z_NULL), or if
993 calls. The fields zalloc, zfree and opaque in strm must be initialized
994 before the call. If zalloc and zfree are Z_NULL, then the default library-