diff options
author | Julian Seward <jseward@acm.org> | 2000-06-24 22:13:13 +0200 |
---|---|---|
committer | Julian Seward <jseward@acm.org> | 2000-06-24 22:13:13 +0200 |
commit | 795b859eee96c700e8f3c3fe68e6a9a39d95797c (patch) | |
tree | 48f8a731cd5ec2f5f15c6d99f2207ebf4a1f35f6 /CHANGES | |
parent | f93cd82a9a7094ad90fd19bbc6ccf6f4627f8060 (diff) | |
download | bzip2-795b859eee96c700e8f3c3fe68e6a9a39d95797c.tar.gz bzip2-795b859eee96c700e8f3c3fe68e6a9a39d95797c.tar.bz2 bzip2-795b859eee96c700e8f3c3fe68e6a9a39d95797c.zip |
bzip2-1.0.1bzip2-1.0.1
Diffstat (limited to 'CHANGES')
-rw-r--r-- | CHANGES | 67 |
1 files changed, 67 insertions, 0 deletions
@@ -98,3 +98,70 @@ functioning of the bzip2 program or library. Added a couple of casts | |||
98 | so the library compiles without warnings at level 3 in MS Visual | 98 | so the library compiles without warnings at level 3 in MS Visual |
99 | Studio 6.0. Included a Y2K statement in the file Y2K_INFO. All other | 99 | Studio 6.0. Included a Y2K statement in the file Y2K_INFO. All other |
100 | changes are minor documentation changes. | 100 | changes are minor documentation changes. |
101 | |||
102 | 1.0 | ||
103 | ~~~ | ||
104 | Several minor bugfixes and enhancements: | ||
105 | |||
106 | * Large file support. The library uses 64-bit counters to | ||
107 | count the volume of data passing through it. bzip2.c | ||
108 | is now compiled with -D_FILE_OFFSET_BITS=64 to get large | ||
109 | file support from the C library. -v correctly prints out | ||
110 | file sizes greater than 4 gigabytes. All these changes have | ||
111 | been made without assuming a 64-bit platform or a C compiler | ||
112 | which supports 64-bit ints, so, except for the C library | ||
113 | aspect, they are fully portable. | ||
114 | |||
115 | * Decompression robustness. The library/program should be | ||
116 | robust to any corruption of compressed data, detecting and | ||
117 | handling _all_ corruption, instead of merely relying on | ||
118 | the CRCs. What this means is that the program should | ||
119 | never crash, given corrupted data, and the library should | ||
120 | always return BZ_DATA_ERROR. | ||
121 | |||
122 | * Fixed an obscure race-condition bug only ever observed on | ||
123 | Solaris, in which, if you were very unlucky and issued | ||
124 | control-C at exactly the wrong time, both input and output | ||
125 | files would be deleted. | ||
126 | |||
127 | * Don't run out of file handles on test/decompression when | ||
128 | large numbers of files have invalid magic numbers. | ||
129 | |||
130 | * Avoid library namespace pollution. Prefix all exported | ||
131 | symbols with BZ2_. | ||
132 | |||
133 | * Minor sorting enhancements from my DCC2000 paper. | ||
134 | |||
135 | * Advance the version number to 1.0, so as to counteract the | ||
136 | (false-in-this-case) impression some people have that programs | ||
137 | with version numbers less than 1.0 are in someway, experimental, | ||
138 | pre-release versions. | ||
139 | |||
140 | * Create an initial Makefile-libbz2_so to build a shared library. | ||
141 | Yes, I know I should really use libtool et al ... | ||
142 | |||
143 | * Make the program exit with 2 instead of 0 when decompression | ||
144 | fails due to a bad magic number (ie, an invalid bzip2 header). | ||
145 | Also exit with 1 (as the manual claims :-) whenever a diagnostic | ||
146 | message would have been printed AND the corresponding operation | ||
147 | is aborted, for example | ||
148 | bzip2: Output file xx already exists. | ||
149 | When a diagnostic message is printed but the operation is not | ||
150 | aborted, for example | ||
151 | bzip2: Can't guess original name for wurble -- using wurble.out | ||
152 | then the exit value 0 is returned, unless some other problem is | ||
153 | also detected. | ||
154 | |||
155 | I think it corresponds more closely to what the manual claims now. | ||
156 | |||
157 | |||
158 | 1.0.1 | ||
159 | ~~~~~ | ||
160 | * Modified dlltest.c so it uses the new BZ2_ naming scheme. | ||
161 | * Modified makefile-msc to fix minor build probs on Win2k. | ||
162 | * Updated README.COMPILATION.PROBLEMS. | ||
163 | |||
164 | There are no functionality changes or bug fixes relative to version | ||
165 | 1.0.0. This is just a documentation update + a fix for minor Win32 | ||
166 | build problems. For almost everyone, upgrading from 1.0.0 to 1.0.1 is | ||
167 | utterly pointless. Don't bother. | ||