home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!charon.amdahl.com!pacbell.com!ames!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!usc!elroy.jpl.nasa.gov!nntp-server.caltech.edu!madler
- From: madler@cco.caltech.edu (Mark Adler)
- Newsgroups: comp.compression
- Subject: Re: compressed files salvagable?
- Date: 6 Nov 1992 18:00:18 GMT
- Organization: California Institute of Technology, Pasadena
- Lines: 20
- Distribution: usa
- Message-ID: <1debriINNsmk@gap.caltech.edu>
- References: <140438@lll-winken.LLNL.GOV> <1d75b6INN7t8@gap.caltech.edu> <4bqM037hb8ds00@amdahl.uts.amdahl.com>
- NNTP-Posting-Host: sandman.caltech.edu
- Keywords: lempel-ziv, compression, compress(1)
-
-
- >> Most versions will also reset the table when the compression worsens, so
- >> it would be possible for compress to reset before it fills up. In this case
-
- Actually, no. From the comments in compress.c:
-
- * to a faster exclusive-or manipulation. Also do block compression with
- * an adaptive reset, whereby the code table is cleared when the compression
- * ratio decreases, but after the table fills. The variable-length output
- * codes are re-sized at this point, and a special CLEAR code is generated
-
- >> It's also possible that the entire lost block was composed of an already-
- >> seen prefix. The odds of this happening are pretty slim though. You may
-
- I don't understand this comment. As far as I can tell by perusing the
- source, clear really means clear, and there is no history of the file
- kept from before that point.
-
- Mark Adler
- madler@cco.caltech.edu
-