Counter Strike : Global Offensive Source Code
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

63 lines
3.0 KiB

  1. Puff -- A Simple Inflate
  2. 3 Mar 2003
  3. Mark Adler
  4. [email protected]
  5. What this is --
  6. puff.c provides the routine puff() to decompress the deflate data format. It
  7. does so more slowly than zlib, but the code is about one-fifth the size of the
  8. inflate code in zlib, and written to be very easy to read.
  9. Why I wrote this --
  10. puff.c was written to document the deflate format unambiguously, by virtue of
  11. being working C code. It is meant to supplement RFC 1951, which formally
  12. describes the deflate format. I have received many questions on details of the
  13. deflate format, and I hope that reading this code will answer those questions.
  14. puff.c is heavily commented with details of the deflate format, especially
  15. those little nooks and cranies of the format that might not be obvious from a
  16. specification.
  17. puff.c may also be useful in applications where code size or memory usage is a
  18. very limited resource, and speed is not as important.
  19. How to use it --
  20. Well, most likely you should just be reading puff.c and using zlib for actual
  21. applications, but if you must ...
  22. Include puff.h in your code, which provides this prototype:
  23. int puff(unsigned char *dest, /* pointer to destination pointer */
  24. unsigned long *destlen, /* amount of output space */
  25. unsigned char *source, /* pointer to source data pointer */
  26. unsigned long *sourcelen); /* amount of input available */
  27. Then you can call puff() to decompress a deflate stream that is in memory in
  28. its entirety at source, to a sufficiently sized block of memory for the
  29. decompressed data at dest. puff() is the only external symbol in puff.c The
  30. only C library functions that puff.c needs are setjmp() and longjmp(), which
  31. are used to simplify error checking in the code to improve readabilty. puff.c
  32. does no memory allocation, and uses less than 2K bytes off of the stack.
  33. If destlen is not enough space for the uncompressed data, then inflate will
  34. return an error without writing more than destlen bytes. Note that this means
  35. that in order to decompress the deflate data successfully, you need to know
  36. the size of the uncompressed data ahead of time.
  37. If needed, puff() can determine the size of the uncompressed data with no
  38. output space. This is done by passing dest equal to (unsigned char *)0. Then
  39. the initial value of *destlen is ignored and *destlen is set to the length of
  40. the uncompressed data. So if the size of the uncompressed data is not known,
  41. then two passes of puff() can be used--first to determine the size, and second
  42. to do the actual inflation after allocating the appropriate memory. Not
  43. pretty, but it works. (This is one of the reasons you should be using zlib.)
  44. The deflate format is self-terminating. If the deflate stream does not end
  45. in *sourcelen bytes, puff() will return an error without reading at or past
  46. endsource.
  47. On return, *sourcelen is updated to the amount of input data consumed, and
  48. *destlen is updated to the size of the uncompressed data. See the comments
  49. in puff.c for the possible return codes for puff().