Mercurial > hg > sv-dependency-builds

annotate src/zlib-1.2.7/examples/zlib_how.html @ 169:223a55898ab9 tip default

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Add null config files
author Chris Cannam <cannam@all-day-breakfast.com>
date Mon, 02 Mar 2020 14:03:47 +0000
parents 8a15ff55d9af
children
rev   line source
cannam@89 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
cannam@89 2 "http://www.w3.org/TR/REC-html40/loose.dtd">
cannam@89 3 <html>
cannam@89 4 <head>
cannam@89 5 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
cannam@89 6 <title>zlib Usage Example</title>
cannam@89 7 <!-- Copyright (c) 2004, 2005 Mark Adler. -->
cannam@89 8 </head>
cannam@89 9 <body bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#00A000">
cannam@89 10 <h2 align="center"> zlib Usage Example </h2>
cannam@89 11 We often get questions about how the <tt>deflate()</tt> and <tt>inflate()</tt> functions should be used.
cannam@89 12 Users wonder when they should provide more input, when they should use more output,
cannam@89 13 what to do with a <tt>Z_BUF_ERROR</tt>, how to make sure the process terminates properly, and
cannam@89 14 so on. So for those who have read <tt>zlib.h</tt> (a few times), and
cannam@89 15 would like further edification, below is an annotated example in C of simple routines to compress and decompress
cannam@89 16 from an input file to an output file using <tt>deflate()</tt> and <tt>inflate()</tt> respectively. The
cannam@89 17 annotations are interspersed between lines of the code. So please read between the lines.
cannam@89 18 We hope this helps explain some of the intricacies of <em>zlib</em>.
cannam@89 19 <p>
cannam@89 20 Without further adieu, here is the program <a href="zpipe.c"><tt>zpipe.c</tt></a>:
cannam@89 21 <pre><b>
cannam@89 22 /* zpipe.c: example of proper use of zlib's inflate() and deflate()
cannam@89 23 Not copyrighted -- provided to the public domain
cannam@89 24 Version 1.4 11 December 2005 Mark Adler */
cannam@89 25
cannam@89 26 /* Version history:
cannam@89 27 1.0 30 Oct 2004 First version
cannam@89 28 1.1 8 Nov 2004 Add void casting for unused return values
cannam@89 29 Use switch statement for inflate() return values
cannam@89 30 1.2 9 Nov 2004 Add assertions to document zlib guarantees
cannam@89 31 1.3 6 Apr 2005 Remove incorrect assertion in inf()
cannam@89 32 1.4 11 Dec 2005 Add hack to avoid MSDOS end-of-line conversions
cannam@89 33 Avoid some compiler warnings for input and output buffers
cannam@89 34 */
cannam@89 35 </b></pre><!-- -->
cannam@89 36 We now include the header files for the required definitions. From
cannam@89 37 <tt>stdio.h</tt> we use <tt>fopen()</tt>, <tt>fread()</tt>, <tt>fwrite()</tt>,
cannam@89 38 <tt>feof()</tt>, <tt>ferror()</tt>, and <tt>fclose()</tt> for file i/o, and
cannam@89 39 <tt>fputs()</tt> for error messages. From <tt>string.h</tt> we use
cannam@89 40 <tt>strcmp()</tt> for command line argument processing.
cannam@89 41 From <tt>assert.h</tt> we use the <tt>assert()</tt> macro.
cannam@89 42 From <tt>zlib.h</tt>
cannam@89 43 we use the basic compression functions <tt>deflateInit()</tt>,
cannam@89 44 <tt>deflate()</tt>, and <tt>deflateEnd()</tt>, and the basic decompression
cannam@89 45 functions <tt>inflateInit()</tt>, <tt>inflate()</tt>, and
cannam@89 46 <tt>inflateEnd()</tt>.
cannam@89 47 <pre><b>
cannam@89 48 #include &lt;stdio.h&gt;
cannam@89 49 #include &lt;string.h&gt;
cannam@89 50 #include &lt;assert.h&gt;
cannam@89 51 #include "zlib.h"
cannam@89 52 </b></pre><!-- -->
cannam@89 53 This is an ugly hack required to avoid corruption of the input and output data on
cannam@89 54 Windows/MS-DOS systems. Without this, those systems would assume that the input and output
cannam@89 55 files are text, and try to convert the end-of-line characters from one standard to
cannam@89 56 another. That would corrupt binary data, and in particular would render the compressed data unusable.
cannam@89 57 This sets the input and output to binary which suppresses the end-of-line conversions.
cannam@89 58 <tt>SET_BINARY_MODE()</tt> will be used later on <tt>stdin</tt> and <tt>stdout</tt>, at the beginning of <tt>main()</tt>.
cannam@89 59 <pre><b>
cannam@89 60 #if defined(MSDOS) || defined(OS2) || defined(WIN32) || defined(__CYGWIN__)
cannam@89 61 # include &lt;fcntl.h&gt;
cannam@89 62 # include &lt;io.h&gt;
cannam@89 63 # define SET_BINARY_MODE(file) setmode(fileno(file), O_BINARY)
cannam@89 64 #else
cannam@89 65 # define SET_BINARY_MODE(file)
cannam@89 66 #endif
cannam@89 67 </b></pre><!-- -->
cannam@89 68 <tt>CHUNK</tt> is simply the buffer size for feeding data to and pulling data
cannam@89 69 from the <em>zlib</em> routines. Larger buffer sizes would be more efficient,
cannam@89 70 especially for <tt>inflate()</tt>. If the memory is available, buffers sizes
cannam@89 71 on the order of 128K or 256K bytes should be used.
cannam@89 72 <pre><b>
cannam@89 73 #define CHUNK 16384
cannam@89 74 </b></pre><!-- -->
cannam@89 75 The <tt>def()</tt> routine compresses data from an input file to an output file. The output data
cannam@89 76 will be in the <em>zlib</em> format, which is different from the <em>gzip</em> or <em>zip</em>
cannam@89 77 formats. The <em>zlib</em> format has a very small header of only two bytes to identify it as
cannam@89 78 a <em>zlib</em> stream and to provide decoding information, and a four-byte trailer with a fast
cannam@89 79 check value to verify the integrity of the uncompressed data after decoding.
cannam@89 80 <pre><b>
cannam@89 81 /* Compress from file source to file dest until EOF on source.
cannam@89 82 def() returns Z_OK on success, Z_MEM_ERROR if memory could not be
cannam@89 83 allocated for processing, Z_STREAM_ERROR if an invalid compression
cannam@89 84 level is supplied, Z_VERSION_ERROR if the version of zlib.h and the
cannam@89 85 version of the library linked do not match, or Z_ERRNO if there is
cannam@89 86 an error reading or writing the files. */
cannam@89 87 int def(FILE *source, FILE *dest, int level)
cannam@89 88 {
cannam@89 89 </b></pre>
cannam@89 90 Here are the local variables for <tt>def()</tt>. <tt>ret</tt> will be used for <em>zlib</em>
cannam@89 91 return codes. <tt>flush</tt> will keep track of the current flushing state for <tt>deflate()</tt>,
cannam@89 92 which is either no flushing, or flush to completion after the end of the input file is reached.
cannam@89 93 <tt>have</tt> is the amount of data returned from <tt>deflate()</tt>. The <tt>strm</tt> structure
cannam@89 94 is used to pass information to and from the <em>zlib</em> routines, and to maintain the
cannam@89 95 <tt>deflate()</tt> state. <tt>in</tt> and <tt>out</tt> are the input and output buffers for
cannam@89 96 <tt>deflate()</tt>.
cannam@89 97 <pre><b>
cannam@89 98 int ret, flush;
cannam@89 99 unsigned have;
cannam@89 100 z_stream strm;
cannam@89 101 unsigned char in[CHUNK];
cannam@89 102 unsigned char out[CHUNK];
cannam@89 103 </b></pre><!-- -->
cannam@89 104 The first thing we do is to initialize the <em>zlib</em> state for compression using
cannam@89 105 <tt>deflateInit()</tt>. This must be done before the first use of <tt>deflate()</tt>.
cannam@89 106 The <tt>zalloc</tt>, <tt>zfree</tt>, and <tt>opaque</tt> fields in the <tt>strm</tt>
cannam@89 107 structure must be initialized before calling <tt>deflateInit()</tt>. Here they are
cannam@89 108 set to the <em>zlib</em> constant <tt>Z_NULL</tt> to request that <em>zlib</em> use
cannam@89 109 the default memory allocation routines. An application may also choose to provide
cannam@89 110 custom memory allocation routines here. <tt>deflateInit()</tt> will allocate on the
cannam@89 111 order of 256K bytes for the internal state.
cannam@89 112 (See <a href="zlib_tech.html"><em>zlib Technical Details</em></a>.)
cannam@89 113 <p>
cannam@89 114 <tt>deflateInit()</tt> is called with a pointer to the structure to be initialized and
cannam@89 115 the compression level, which is an integer in the range of -1 to 9. Lower compression
cannam@89 116 levels result in faster execution, but less compression. Higher levels result in
cannam@89 117 greater compression, but slower execution. The <em>zlib</em> constant Z_DEFAULT_COMPRESSION,
cannam@89 118 equal to -1,
cannam@89 119 provides a good compromise between compression and speed and is equivalent to level 6.
cannam@89 120 Level 0 actually does no compression at all, and in fact expands the data slightly to produce
cannam@89 121 the <em>zlib</em> format (it is not a byte-for-byte copy of the input).
cannam@89 122 More advanced applications of <em>zlib</em>
cannam@89 123 may use <tt>deflateInit2()</tt> here instead. Such an application may want to reduce how
cannam@89 124 much memory will be used, at some price in compression. Or it may need to request a
cannam@89 125 <em>gzip</em> header and trailer instead of a <em>zlib</em> header and trailer, or raw
cannam@89 126 encoding with no header or trailer at all.
cannam@89 127 <p>
cannam@89 128 We must check the return value of <tt>deflateInit()</tt> against the <em>zlib</em> constant
cannam@89 129 <tt>Z_OK</tt> to make sure that it was able to
cannam@89 130 allocate memory for the internal state, and that the provided arguments were valid.
cannam@89 131 <tt>deflateInit()</tt> will also check that the version of <em>zlib</em> that the <tt>zlib.h</tt>
cannam@89 132 file came from matches the version of <em>zlib</em> actually linked with the program. This
cannam@89 133 is especially important for environments in which <em>zlib</em> is a shared library.
cannam@89 134 <p>
cannam@89 135 Note that an application can initialize multiple, independent <em>zlib</em> streams, which can
cannam@89 136 operate in parallel. The state information maintained in the structure allows the <em>zlib</em>
cannam@89 137 routines to be reentrant.
cannam@89 138 <pre><b>
cannam@89 139 /* allocate deflate state */
cannam@89 140 strm.zalloc = Z_NULL;
cannam@89 141 strm.zfree = Z_NULL;
cannam@89 142 strm.opaque = Z_NULL;
cannam@89 143 ret = deflateInit(&amp;strm, level);
cannam@89 144 if (ret != Z_OK)
cannam@89 145 return ret;
cannam@89 146 </b></pre><!-- -->
cannam@89 147 With the pleasantries out of the way, now we can get down to business. The outer <tt>do</tt>-loop
cannam@89 148 reads all of the input file and exits at the bottom of the loop once end-of-file is reached.
cannam@89 149 This loop contains the only call of <tt>deflate()</tt>. So we must make sure that all of the
cannam@89 150 input data has been processed and that all of the output data has been generated and consumed
cannam@89 151 before we fall out of the loop at the bottom.
cannam@89 152 <pre><b>
cannam@89 153 /* compress until end of file */
cannam@89 154 do {
cannam@89 155 </b></pre>
cannam@89 156 We start off by reading data from the input file. The number of bytes read is put directly
cannam@89 157 into <tt>avail_in</tt>, and a pointer to those bytes is put into <tt>next_in</tt>. We also
cannam@89 158 check to see if end-of-file on the input has been reached. If we are at the end of file, then <tt>flush</tt> is set to the
cannam@89 159 <em>zlib</em> constant <tt>Z_FINISH</tt>, which is later passed to <tt>deflate()</tt> to
cannam@89 160 indicate that this is the last chunk of input data to compress. We need to use <tt>feof()</tt>
cannam@89 161 to check for end-of-file as opposed to seeing if fewer than <tt>CHUNK</tt> bytes have been read. The
cannam@89 162 reason is that if the input file length is an exact multiple of <tt>CHUNK</tt>, we will miss
cannam@89 163 the fact that we got to the end-of-file, and not know to tell <tt>deflate()</tt> to finish
cannam@89 164 up the compressed stream. If we are not yet at the end of the input, then the <em>zlib</em>
cannam@89 165 constant <tt>Z_NO_FLUSH</tt> will be passed to <tt>deflate</tt> to indicate that we are still
cannam@89 166 in the middle of the uncompressed data.
cannam@89 167 <p>
cannam@89 168 If there is an error in reading from the input file, the process is aborted with
cannam@89 169 <tt>deflateEnd()</tt> being called to free the allocated <em>zlib</em> state before returning
cannam@89 170 the error. We wouldn't want a memory leak, now would we? <tt>deflateEnd()</tt> can be called
cannam@89 171 at any time after the state has been initialized. Once that's done, <tt>deflateInit()</tt> (or
cannam@89 172 <tt>deflateInit2()</tt>) would have to be called to start a new compression process. There is
cannam@89 173 no point here in checking the <tt>deflateEnd()</tt> return code. The deallocation can't fail.
cannam@89 174 <pre><b>
cannam@89 175 strm.avail_in = fread(in, 1, CHUNK, source);
cannam@89 176 if (ferror(source)) {
cannam@89 177 (void)deflateEnd(&amp;strm);
cannam@89 178 return Z_ERRNO;
cannam@89 179 }
cannam@89 180 flush = feof(source) ? Z_FINISH : Z_NO_FLUSH;
cannam@89 181 strm.next_in = in;
cannam@89 182 </b></pre><!-- -->
cannam@89 183 The inner <tt>do</tt>-loop passes our chunk of input data to <tt>deflate()</tt>, and then
cannam@89 184 keeps calling <tt>deflate()</tt> until it is done producing output. Once there is no more
cannam@89 185 new output, <tt>deflate()</tt> is guaranteed to have consumed all of the input, i.e.,
cannam@89 186 <tt>avail_in</tt> will be zero.
cannam@89 187 <pre><b>
cannam@89 188 /* run deflate() on input until output buffer not full, finish
cannam@89 189 compression if all of source has been read in */
cannam@89 190 do {
cannam@89 191 </b></pre>
cannam@89 192 Output space is provided to <tt>deflate()</tt> by setting <tt>avail_out</tt> to the number
cannam@89 193 of available output bytes and <tt>next_out</tt> to a pointer to that space.
cannam@89 194 <pre><b>
cannam@89 195 strm.avail_out = CHUNK;
cannam@89 196 strm.next_out = out;
cannam@89 197 </b></pre>
cannam@89 198 Now we call the compression engine itself, <tt>deflate()</tt>. It takes as many of the
cannam@89 199 <tt>avail_in</tt> bytes at <tt>next_in</tt> as it can process, and writes as many as
cannam@89 200 <tt>avail_out</tt> bytes to <tt>next_out</tt>. Those counters and pointers are then
cannam@89 201 updated past the input data consumed and the output data written. It is the amount of
cannam@89 202 output space available that may limit how much input is consumed.
cannam@89 203 Hence the inner loop to make sure that
cannam@89 204 all of the input is consumed by providing more output space each time. Since <tt>avail_in</tt>
cannam@89 205 and <tt>next_in</tt> are updated by <tt>deflate()</tt>, we don't have to mess with those
cannam@89 206 between <tt>deflate()</tt> calls until it's all used up.
cannam@89 207 <p>
cannam@89 208 The parameters to <tt>deflate()</tt> are a pointer to the <tt>strm</tt> structure containing
cannam@89 209 the input and output information and the internal compression engine state, and a parameter
cannam@89 210 indicating whether and how to flush data to the output. Normally <tt>deflate</tt> will consume
cannam@89 211 several K bytes of input data before producing any output (except for the header), in order
cannam@89 212 to accumulate statistics on the data for optimum compression. It will then put out a burst of
cannam@89 213 compressed data, and proceed to consume more input before the next burst. Eventually,
cannam@89 214 <tt>deflate()</tt>
cannam@89 215 must be told to terminate the stream, complete the compression with provided input data, and
cannam@89 216 write out the trailer check value. <tt>deflate()</tt> will continue to compress normally as long
cannam@89 217 as the flush parameter is <tt>Z_NO_FLUSH</tt>. Once the <tt>Z_FINISH</tt> parameter is provided,
cannam@89 218 <tt>deflate()</tt> will begin to complete the compressed output stream. However depending on how
cannam@89 219 much output space is provided, <tt>deflate()</tt> may have to be called several times until it
cannam@89 220 has provided the complete compressed stream, even after it has consumed all of the input. The flush
cannam@89 221 parameter must continue to be <tt>Z_FINISH</tt> for those subsequent calls.
cannam@89 222 <p>
cannam@89 223 There are other values of the flush parameter that are used in more advanced applications. You can
cannam@89 224 force <tt>deflate()</tt> to produce a burst of output that encodes all of the input data provided
cannam@89 225 so far, even if it wouldn't have otherwise, for example to control data latency on a link with
cannam@89 226 compressed data. You can also ask that <tt>deflate()</tt> do that as well as erase any history up to
cannam@89 227 that point so that what follows can be decompressed independently, for example for random access
cannam@89 228 applications. Both requests will degrade compression by an amount depending on how often such
cannam@89 229 requests are made.
cannam@89 230 <p>
cannam@89 231 <tt>deflate()</tt> has a return value that can indicate errors, yet we do not check it here. Why
cannam@89 232 not? Well, it turns out that <tt>deflate()</tt> can do no wrong here. Let's go through
cannam@89 233 <tt>deflate()</tt>'s return values and dispense with them one by one. The possible values are
cannam@89 234 <tt>Z_OK</tt>, <tt>Z_STREAM_END</tt>, <tt>Z_STREAM_ERROR</tt>, or <tt>Z_BUF_ERROR</tt>. <tt>Z_OK</tt>
cannam@89 235 is, well, ok. <tt>Z_STREAM_END</tt> is also ok and will be returned for the last call of
cannam@89 236 <tt>deflate()</tt>. This is already guaranteed by calling <tt>deflate()</tt> with <tt>Z_FINISH</tt>
cannam@89 237 until it has no more output. <tt>Z_STREAM_ERROR</tt> is only possible if the stream is not
cannam@89 238 initialized properly, but we did initialize it properly. There is no harm in checking for
cannam@89 239 <tt>Z_STREAM_ERROR</tt> here, for example to check for the possibility that some
cannam@89 240 other part of the application inadvertently clobbered the memory containing the <em>zlib</em> state.
cannam@89 241 <tt>Z_BUF_ERROR</tt> will be explained further below, but
cannam@89 242 suffice it to say that this is simply an indication that <tt>deflate()</tt> could not consume
cannam@89 243 more input or produce more output. <tt>deflate()</tt> can be called again with more output space
cannam@89 244 or more available input, which it will be in this code.
cannam@89 245 <pre><b>
cannam@89 246 ret = deflate(&amp;strm, flush); /* no bad return value */
cannam@89 247 assert(ret != Z_STREAM_ERROR); /* state not clobbered */
cannam@89 248 </b></pre>
cannam@89 249 Now we compute how much output <tt>deflate()</tt> provided on the last call, which is the
cannam@89 250 difference between how much space was provided before the call, and how much output space
cannam@89 251 is still available after the call. Then that data, if any, is written to the output file.
cannam@89 252 We can then reuse the output buffer for the next call of <tt>deflate()</tt>. Again if there
cannam@89 253 is a file i/o error, we call <tt>deflateEnd()</tt> before returning to avoid a memory leak.
cannam@89 254 <pre><b>
cannam@89 255 have = CHUNK - strm.avail_out;
cannam@89 256 if (fwrite(out, 1, have, dest) != have || ferror(dest)) {
cannam@89 257 (void)deflateEnd(&amp;strm);
cannam@89 258 return Z_ERRNO;
cannam@89 259 }
cannam@89 260 </b></pre>
cannam@89 261 The inner <tt>do</tt>-loop is repeated until the last <tt>deflate()</tt> call fails to fill the
cannam@89 262 provided output buffer. Then we know that <tt>deflate()</tt> has done as much as it can with
cannam@89 263 the provided input, and that all of that input has been consumed. We can then fall out of this
cannam@89 264 loop and reuse the input buffer.
cannam@89 265 <p>
cannam@89 266 The way we tell that <tt>deflate()</tt> has no more output is by seeing that it did not fill
cannam@89 267 the output buffer, leaving <tt>avail_out</tt> greater than zero. However suppose that
cannam@89 268 <tt>deflate()</tt> has no more output, but just so happened to exactly fill the output buffer!
cannam@89 269 <tt>avail_out</tt> is zero, and we can't tell that <tt>deflate()</tt> has done all it can.
cannam@89 270 As far as we know, <tt>deflate()</tt>
cannam@89 271 has more output for us. So we call it again. But now <tt>deflate()</tt> produces no output
cannam@89 272 at all, and <tt>avail_out</tt> remains unchanged as <tt>CHUNK</tt>. That <tt>deflate()</tt> call
cannam@89 273 wasn't able to do anything, either consume input or produce output, and so it returns
cannam@89 274 <tt>Z_BUF_ERROR</tt>. (See, I told you I'd cover this later.) However this is not a problem at
cannam@89 275 all. Now we finally have the desired indication that <tt>deflate()</tt> is really done,
cannam@89 276 and so we drop out of the inner loop to provide more input to <tt>deflate()</tt>.
cannam@89 277 <p>
cannam@89 278 With <tt>flush</tt> set to <tt>Z_FINISH</tt>, this final set of <tt>deflate()</tt> calls will
cannam@89 279 complete the output stream. Once that is done, subsequent calls of <tt>deflate()</tt> would return
cannam@89 280 <tt>Z_STREAM_ERROR</tt> if the flush parameter is not <tt>Z_FINISH</tt>, and do no more processing
cannam@89 281 until the state is reinitialized.
cannam@89 282 <p>
cannam@89 283 Some applications of <em>zlib</em> have two loops that call <tt>deflate()</tt>
cannam@89 284 instead of the single inner loop we have here. The first loop would call
cannam@89 285 without flushing and feed all of the data to <tt>deflate()</tt>. The second loop would call
cannam@89 286 <tt>deflate()</tt> with no more
cannam@89 287 data and the <tt>Z_FINISH</tt> parameter to complete the process. As you can see from this
cannam@89 288 example, that can be avoided by simply keeping track of the current flush state.
cannam@89 289 <pre><b>
cannam@89 290 } while (strm.avail_out == 0);
cannam@89 291 assert(strm.avail_in == 0); /* all input will be used */
cannam@89 292 </b></pre><!-- -->
cannam@89 293 Now we check to see if we have already processed all of the input file. That information was
cannam@89 294 saved in the <tt>flush</tt> variable, so we see if that was set to <tt>Z_FINISH</tt>. If so,
cannam@89 295 then we're done and we fall out of the outer loop. We're guaranteed to get <tt>Z_STREAM_END</tt>
cannam@89 296 from the last <tt>deflate()</tt> call, since we ran it until the last chunk of input was
cannam@89 297 consumed and all of the output was generated.
cannam@89 298 <pre><b>
cannam@89 299 /* done when last data in file processed */
cannam@89 300 } while (flush != Z_FINISH);
cannam@89 301 assert(ret == Z_STREAM_END); /* stream will be complete */
cannam@89 302 </b></pre><!-- -->
cannam@89 303 The process is complete, but we still need to deallocate the state to avoid a memory leak
cannam@89 304 (or rather more like a memory hemorrhage if you didn't do this). Then
cannam@89 305 finally we can return with a happy return value.
cannam@89 306 <pre><b>
cannam@89 307 /* clean up and return */
cannam@89 308 (void)deflateEnd(&amp;strm);
cannam@89 309 return Z_OK;
cannam@89 310 }
cannam@89 311 </b></pre><!-- -->
cannam@89 312 Now we do the same thing for decompression in the <tt>inf()</tt> routine. <tt>inf()</tt>
cannam@89 313 decompresses what is hopefully a valid <em>zlib</em> stream from the input file and writes the
cannam@89 314 uncompressed data to the output file. Much of the discussion above for <tt>def()</tt>
cannam@89 315 applies to <tt>inf()</tt> as well, so the discussion here will focus on the differences between
cannam@89 316 the two.
cannam@89 317 <pre><b>
cannam@89 318 /* Decompress from file source to file dest until stream ends or EOF.
cannam@89 319 inf() returns Z_OK on success, Z_MEM_ERROR if memory could not be
cannam@89 320 allocated for processing, Z_DATA_ERROR if the deflate data is
cannam@89 321 invalid or incomplete, Z_VERSION_ERROR if the version of zlib.h and
cannam@89 322 the version of the library linked do not match, or Z_ERRNO if there
cannam@89 323 is an error reading or writing the files. */
cannam@89 324 int inf(FILE *source, FILE *dest)
cannam@89 325 {
cannam@89 326 </b></pre>
cannam@89 327 The local variables have the same functionality as they do for <tt>def()</tt>. The
cannam@89 328 only difference is that there is no <tt>flush</tt> variable, since <tt>inflate()</tt>
cannam@89 329 can tell from the <em>zlib</em> stream itself when the stream is complete.
cannam@89 330 <pre><b>
cannam@89 331 int ret;
cannam@89 332 unsigned have;
cannam@89 333 z_stream strm;
cannam@89 334 unsigned char in[CHUNK];
cannam@89 335 unsigned char out[CHUNK];
cannam@89 336 </b></pre><!-- -->
cannam@89 337 The initialization of the state is the same, except that there is no compression level,
cannam@89 338 of course, and two more elements of the structure are initialized. <tt>avail_in</tt>
cannam@89 339 and <tt>next_in</tt> must be initialized before calling <tt>inflateInit()</tt>. This
cannam@89 340 is because the application has the option to provide the start of the zlib stream in
cannam@89 341 order for <tt>inflateInit()</tt> to have access to information about the compression
cannam@89 342 method to aid in memory allocation. In the current implementation of <em>zlib</em>
cannam@89 343 (up through versions 1.2.x), the method-dependent memory allocations are deferred to the first call of
cannam@89 344 <tt>inflate()</tt> anyway. However those fields must be initialized since later versions
cannam@89 345 of <em>zlib</em> that provide more compression methods may take advantage of this interface.
cannam@89 346 In any case, no decompression is performed by <tt>inflateInit()</tt>, so the
cannam@89 347 <tt>avail_out</tt> and <tt>next_out</tt> fields do not need to be initialized before calling.
cannam@89 348 <p>
cannam@89 349 Here <tt>avail_in</tt> is set to zero and <tt>next_in</tt> is set to <tt>Z_NULL</tt> to
cannam@89 350 indicate that no input data is being provided.
cannam@89 351 <pre><b>
cannam@89 352 /* allocate inflate state */
cannam@89 353 strm.zalloc = Z_NULL;
cannam@89 354 strm.zfree = Z_NULL;
cannam@89 355 strm.opaque = Z_NULL;
cannam@89 356 strm.avail_in = 0;
cannam@89 357 strm.next_in = Z_NULL;
cannam@89 358 ret = inflateInit(&amp;strm);
cannam@89 359 if (ret != Z_OK)
cannam@89 360 return ret;
cannam@89 361 </b></pre><!-- -->
cannam@89 362 The outer <tt>do</tt>-loop decompresses input until <tt>inflate()</tt> indicates
cannam@89 363 that it has reached the end of the compressed data and has produced all of the uncompressed
cannam@89 364 output. This is in contrast to <tt>def()</tt> which processes all of the input file.
cannam@89 365 If end-of-file is reached before the compressed data self-terminates, then the compressed
cannam@89 366 data is incomplete and an error is returned.
cannam@89 367 <pre><b>
cannam@89 368 /* decompress until deflate stream ends or end of file */
cannam@89 369 do {
cannam@89 370 </b></pre>
cannam@89 371 We read input data and set the <tt>strm</tt> structure accordingly. If we've reached the
cannam@89 372 end of the input file, then we leave the outer loop and report an error, since the
cannam@89 373 compressed data is incomplete. Note that we may read more data than is eventually consumed
cannam@89 374 by <tt>inflate()</tt>, if the input file continues past the <em>zlib</em> stream.
cannam@89 375 For applications where <em>zlib</em> streams are embedded in other data, this routine would
cannam@89 376 need to be modified to return the unused data, or at least indicate how much of the input
cannam@89 377 data was not used, so the application would know where to pick up after the <em>zlib</em> stream.
cannam@89 378 <pre><b>
cannam@89 379 strm.avail_in = fread(in, 1, CHUNK, source);
cannam@89 380 if (ferror(source)) {
cannam@89 381 (void)inflateEnd(&amp;strm);
cannam@89 382 return Z_ERRNO;
cannam@89 383 }
cannam@89 384 if (strm.avail_in == 0)
cannam@89 385 break;
cannam@89 386 strm.next_in = in;
cannam@89 387 </b></pre><!-- -->
cannam@89 388 The inner <tt>do</tt>-loop has the same function it did in <tt>def()</tt>, which is to
cannam@89 389 keep calling <tt>inflate()</tt> until has generated all of the output it can with the
cannam@89 390 provided input.
cannam@89 391 <pre><b>
cannam@89 392 /* run inflate() on input until output buffer not full */
cannam@89 393 do {
cannam@89 394 </b></pre>
cannam@89 395 Just like in <tt>def()</tt>, the same output space is provided for each call of <tt>inflate()</tt>.
cannam@89 396 <pre><b>
cannam@89 397 strm.avail_out = CHUNK;
cannam@89 398 strm.next_out = out;
cannam@89 399 </b></pre>
cannam@89 400 Now we run the decompression engine itself. There is no need to adjust the flush parameter, since
cannam@89 401 the <em>zlib</em> format is self-terminating. The main difference here is that there are
cannam@89 402 return values that we need to pay attention to. <tt>Z_DATA_ERROR</tt>
cannam@89 403 indicates that <tt>inflate()</tt> detected an error in the <em>zlib</em> compressed data format,
cannam@89 404 which means that either the data is not a <em>zlib</em> stream to begin with, or that the data was
cannam@89 405 corrupted somewhere along the way since it was compressed. The other error to be processed is
cannam@89 406 <tt>Z_MEM_ERROR</tt>, which can occur since memory allocation is deferred until <tt>inflate()</tt>
cannam@89 407 needs it, unlike <tt>deflate()</tt>, whose memory is allocated at the start by <tt>deflateInit()</tt>.
cannam@89 408 <p>
cannam@89 409 Advanced applications may use
cannam@89 410 <tt>deflateSetDictionary()</tt> to prime <tt>deflate()</tt> with a set of likely data to improve the
cannam@89 411 first 32K or so of compression. This is noted in the <em>zlib</em> header, so <tt>inflate()</tt>
cannam@89 412 requests that that dictionary be provided before it can start to decompress. Without the dictionary,
cannam@89 413 correct decompression is not possible. For this routine, we have no idea what the dictionary is,
cannam@89 414 so the <tt>Z_NEED_DICT</tt> indication is converted to a <tt>Z_DATA_ERROR</tt>.
cannam@89 415 <p>
cannam@89 416 <tt>inflate()</tt> can also return <tt>Z_STREAM_ERROR</tt>, which should not be possible here,
cannam@89 417 but could be checked for as noted above for <tt>def()</tt>. <tt>Z_BUF_ERROR</tt> does not need to be
cannam@89 418 checked for here, for the same reasons noted for <tt>def()</tt>. <tt>Z_STREAM_END</tt> will be
cannam@89 419 checked for later.
cannam@89 420 <pre><b>
cannam@89 421 ret = inflate(&amp;strm, Z_NO_FLUSH);
cannam@89 422 assert(ret != Z_STREAM_ERROR); /* state not clobbered */
cannam@89 423 switch (ret) {
cannam@89 424 case Z_NEED_DICT:
cannam@89 425 ret = Z_DATA_ERROR; /* and fall through */
cannam@89 426 case Z_DATA_ERROR:
cannam@89 427 case Z_MEM_ERROR:
cannam@89 428 (void)inflateEnd(&amp;strm);
cannam@89 429 return ret;
cannam@89 430 }
cannam@89 431 </b></pre>
cannam@89 432 The output of <tt>inflate()</tt> is handled identically to that of <tt>deflate()</tt>.
cannam@89 433 <pre><b>
cannam@89 434 have = CHUNK - strm.avail_out;
cannam@89 435 if (fwrite(out, 1, have, dest) != have || ferror(dest)) {
cannam@89 436 (void)inflateEnd(&amp;strm);
cannam@89 437 return Z_ERRNO;
cannam@89 438 }
cannam@89 439 </b></pre>
cannam@89 440 The inner <tt>do</tt>-loop ends when <tt>inflate()</tt> has no more output as indicated
cannam@89 441 by not filling the output buffer, just as for <tt>deflate()</tt>. In this case, we cannot
cannam@89 442 assert that <tt>strm.avail_in</tt> will be zero, since the deflate stream may end before the file
cannam@89 443 does.
cannam@89 444 <pre><b>
cannam@89 445 } while (strm.avail_out == 0);
cannam@89 446 </b></pre><!-- -->
cannam@89 447 The outer <tt>do</tt>-loop ends when <tt>inflate()</tt> reports that it has reached the
cannam@89 448 end of the input <em>zlib</em> stream, has completed the decompression and integrity
cannam@89 449 check, and has provided all of the output. This is indicated by the <tt>inflate()</tt>
cannam@89 450 return value <tt>Z_STREAM_END</tt>. The inner loop is guaranteed to leave <tt>ret</tt>
cannam@89 451 equal to <tt>Z_STREAM_END</tt> if the last chunk of the input file read contained the end
cannam@89 452 of the <em>zlib</em> stream. So if the return value is not <tt>Z_STREAM_END</tt>, the
cannam@89 453 loop continues to read more input.
cannam@89 454 <pre><b>
cannam@89 455 /* done when inflate() says it's done */
cannam@89 456 } while (ret != Z_STREAM_END);
cannam@89 457 </b></pre><!-- -->
cannam@89 458 At this point, decompression successfully completed, or we broke out of the loop due to no
cannam@89 459 more data being available from the input file. If the last <tt>inflate()</tt> return value
cannam@89 460 is not <tt>Z_STREAM_END</tt>, then the <em>zlib</em> stream was incomplete and a data error
cannam@89 461 is returned. Otherwise, we return with a happy return value. Of course, <tt>inflateEnd()</tt>
cannam@89 462 is called first to avoid a memory leak.
cannam@89 463 <pre><b>
cannam@89 464 /* clean up and return */
cannam@89 465 (void)inflateEnd(&amp;strm);
cannam@89 466 return ret == Z_STREAM_END ? Z_OK : Z_DATA_ERROR;
cannam@89 467 }
cannam@89 468 </b></pre><!-- -->
cannam@89 469 That ends the routines that directly use <em>zlib</em>. The following routines make this
cannam@89 470 a command-line program by running data through the above routines from <tt>stdin</tt> to
cannam@89 471 <tt>stdout</tt>, and handling any errors reported by <tt>def()</tt> or <tt>inf()</tt>.
cannam@89 472 <p>
cannam@89 473 <tt>zerr()</tt> is used to interpret the possible error codes from <tt>def()</tt>
cannam@89 474 and <tt>inf()</tt>, as detailed in their comments above, and print out an error message.
cannam@89 475 Note that these are only a subset of the possible return values from <tt>deflate()</tt>
cannam@89 476 and <tt>inflate()</tt>.
cannam@89 477 <pre><b>
cannam@89 478 /* report a zlib or i/o error */
cannam@89 479 void zerr(int ret)
cannam@89 480 {
cannam@89 481 fputs("zpipe: ", stderr);
cannam@89 482 switch (ret) {
cannam@89 483 case Z_ERRNO:
cannam@89 484 if (ferror(stdin))
cannam@89 485 fputs("error reading stdin\n", stderr);
cannam@89 486 if (ferror(stdout))
cannam@89 487 fputs("error writing stdout\n", stderr);
cannam@89 488 break;
cannam@89 489 case Z_STREAM_ERROR:
cannam@89 490 fputs("invalid compression level\n", stderr);
cannam@89 491 break;
cannam@89 492 case Z_DATA_ERROR:
cannam@89 493 fputs("invalid or incomplete deflate data\n", stderr);
cannam@89 494 break;
cannam@89 495 case Z_MEM_ERROR:
cannam@89 496 fputs("out of memory\n", stderr);
cannam@89 497 break;
cannam@89 498 case Z_VERSION_ERROR:
cannam@89 499 fputs("zlib version mismatch!\n", stderr);
cannam@89 500 }
cannam@89 501 }
cannam@89 502 </b></pre><!-- -->
cannam@89 503 Here is the <tt>main()</tt> routine used to test <tt>def()</tt> and <tt>inf()</tt>. The
cannam@89 504 <tt>zpipe</tt> command is simply a compression pipe from <tt>stdin</tt> to <tt>stdout</tt>, if
cannam@89 505 no arguments are given, or it is a decompression pipe if <tt>zpipe -d</tt> is used. If any other
cannam@89 506 arguments are provided, no compression or decompression is performed. Instead a usage
cannam@89 507 message is displayed. Examples are <tt>zpipe < foo.txt > foo.txt.z</tt> to compress, and
cannam@89 508 <tt>zpipe -d < foo.txt.z > foo.txt</tt> to decompress.
cannam@89 509 <pre><b>
cannam@89 510 /* compress or decompress from stdin to stdout */
cannam@89 511 int main(int argc, char **argv)
cannam@89 512 {
cannam@89 513 int ret;
cannam@89 514
cannam@89 515 /* avoid end-of-line conversions */
cannam@89 516 SET_BINARY_MODE(stdin);
cannam@89 517 SET_BINARY_MODE(stdout);
cannam@89 518
cannam@89 519 /* do compression if no arguments */
cannam@89 520 if (argc == 1) {
cannam@89 521 ret = def(stdin, stdout, Z_DEFAULT_COMPRESSION);
cannam@89 522 if (ret != Z_OK)
cannam@89 523 zerr(ret);
cannam@89 524 return ret;
cannam@89 525 }
cannam@89 526
cannam@89 527 /* do decompression if -d specified */
cannam@89 528 else if (argc == 2 &amp;&amp; strcmp(argv[1], "-d") == 0) {
cannam@89 529 ret = inf(stdin, stdout);
cannam@89 530 if (ret != Z_OK)
cannam@89 531 zerr(ret);
cannam@89 532 return ret;
cannam@89 533 }
cannam@89 534
cannam@89 535 /* otherwise, report usage */
cannam@89 536 else {
cannam@89 537 fputs("zpipe usage: zpipe [-d] &lt; source &gt; dest\n", stderr);
cannam@89 538 return 1;
cannam@89 539 }
cannam@89 540 }
cannam@89 541 </b></pre>
cannam@89 542 <hr>
cannam@89 543 <i>Copyright (c) 2004, 2005 by Mark Adler<br>Last modified 11 December 2005</i>
cannam@89 544 </body>
cannam@89 545 </html>