Lines Matching defs:zalloc

98     alloc_func zalloc;  /* used to allocate the internal state */
100     voidpf     opaque;  /* private data object passed to zalloc and zfree */
136    to zero.  The application must initialize zalloc, zfree and opaque before
141    parameter for calls of zalloc and zfree.  This can be useful for custom
145      zalloc must return Z_NULL if there is not enough memory for the object.
146    If zlib is used in a multi-threaded application, zalloc and zfree must be
147    thread safe.  In that case, zlib is thread-safe.  When zalloc and zfree are
151      On 16-bit systems, the functions zalloc and zfree must be able to allocate
154    returned by zalloc for objects of exactly 65536 bytes *must* have their
212 #define Z_NULL  0  /* for initializing zalloc, zfree, opaque */
231    zalloc, zfree and opaque must be initialized before by the caller.  If
232    zalloc and zfree are set to Z_NULL, deflateInit updates them to use default
381    next_in, avail_in, zalloc, zfree and opaque must be initialized before by
385    first call).  If zalloc and zfree are set to Z_NULL, inflateInit updates
547    fields zalloc, zfree and opaque must be initialized before by the caller.
694    (such as zalloc being Z_NULL).  msg is left unchanged in both source and
706    stream state was inconsistent (such as zalloc or state being Z_NULL).
853    fields next_in, avail_in, zalloc, zfree and opaque must be initialized
972    (such as zalloc being Z_NULL).  msg is left unchanged in both source and
984    stream state was inconsistent (such as zalloc or state being Z_NULL).
997    stream state was inconsistent (such as zalloc or state being Z_NULL), or if
1095    calls.  The fields zalloc, zfree and opaque in strm must be initialized
1096    before the call.  If zalloc and zfree are Z_NULL, then the default library-