Lines Matching full:here
20 Without further adieu, here is the program <a href="zpipe.c"><tt>zpipe.c</tt></a>:
72 Here are the local variables for <tt>def()</tt>. <tt>ret</tt> will be used for <em>zlib</em>
89 structure must be initialized before calling <tt>deflateInit()</tt>. Here they are
92 custom memory allocation routines here. <tt>deflateInit()</tt> will allocate on the
105 may use <tt>deflateInit2()</tt> here instead. Such an application may want to reduce how
155 no point here in checking the <tt>deflateEnd()</tt> return code. The deallocation can't fail.
213 <tt>deflate()</tt> has a return value that can indicate errors, yet we do not check it here. Why
214 not? Well, it turns out that <tt>deflate()</tt> can do no wrong here. Let's go through
221 <tt>Z_STREAM_ERROR</tt> here, for example to check for the possibility that some
266 instead of the single inner loop we have here. The first loop would call
297 applies to <tt>inf()</tt> as well, so the discussion here will focus on the differences between
331 Here <tt>avail_in</tt> is set to zero and <tt>next_in</tt> is set to <tt>Z_NULL</tt> to
383 the <em>zlib</em> format is self-terminating. The main difference here is that there are
398 <tt>inflate()</tt> can also return <tt>Z_STREAM_ERROR</tt>, which should not be possible here,
400 checked for here, for the same reasons noted for <tt>def()</tt>. <tt>Z_STREAM_END</tt> will be
485 Here is the <tt>main()</tt> routine used to test <tt>def()</tt> and <tt>inf()</tt>. The
