xz.git - XZ Utils

Age	Commit message (Collapse)	Author	Files	Lines
2016-12-28	liblzma: Avoid multiple definitions of lzma_coder structures.	Lasse Collin	1	-4/+8
	Only one definition was visible in a translation unit. It avoided a few casts and temp variables but seems that this hack doesn't work with link-time optimizations in compilers as it's not C99/C11 compliant. Fixes: http://www.mail-archive.com/xz-devel@tukaani.org/msg00279.html
2012-07-17	liblzma: Make the use of lzma_allocator const-correct.	Lasse Collin	1	-3/+3
	There is a tiny risk of causing breakage: If an application assigns lzma_stream.allocator to a non-const pointer, such code won't compile anymore. I don't know why anyone would do such a thing though, so in practice this shouldn't cause trouble. Thanks to Jan Kratochvil for the patch.
2011-05-17	Add underscores to attributes (__attribute((__foo__))).	Lasse Collin	1	-1/+1

2010-05-26	Rename MIN() and MAX() to my_min() and my_max().	Lasse Collin	1	-1/+1
	This should avoid some minor portability issues.
2009-11-14	Fix a design error in liblzma API.	Lasse Collin	1	-1/+16
	Originally the idea was that using LZMA_FULL_FLUSH with Stream encoder would read the filter chain from the same array that was used to intialize the Stream encoder. Since most apps wouldn't use LZMA_FULL_FLUSH, most apps wouldn't need to keep the filter chain available after initializing the Stream encoder. However, due to my mistake, it actually required keeping the array always available. Since setting the new filter chain via the array used at initialization time is not a nice way to do it for a couple of reasons, this commit ditches it and introduces lzma_filters_update(). This new function replaces also the "persistent" flag used by LZMA2 (and to-be-designed Subblock filter), which was also an ugly thing to do. Thanks to Alexey Tourbin for reminding me about the problem that Stream encoder used to require keeping the filter chain allocated.
2009-04-13	Put the interesting parts of XZ Utils into the public domain.	Lasse Collin	1	-10/+3
	Some minor documentation cleanups were made at the same time.
2008-12-01	Added lzma_delta_coder_memusage() which also validates	Lasse Collin	1	-10/+4
	the options.
2008-09-27	Some API changes, bug fixes, cleanups etc.	Lasse Collin	1	-3/+3

2008-09-13	Renamed constants:	Lasse Collin	1	-1/+1
	- LZMA_VLI_VALUE_MAX -> LZMA_VLI_MAX - LZMA_VLI_VALUE_UNKNOWN -> LZMA_VLI_UNKNOWN - LZMA_HEADER_ERRRO -> LZMA_OPTIONS_ERROR
2008-08-28	Sort of garbage collection commit. :-\| Many things are still	Lasse Collin	1	-0/+21
	broken. API has changed a lot and it will still change a little more here and there. The command line tool doesn't have all the required changes to reflect the API changes, so it's easy to get "internal error" or trigger assertions.
2008-06-18	Update the code to mostly match the new simpler file format	Lasse Collin	1	-3/+4
	specification. Simplify things by removing most of the support for known uncompressed size in most places. There are some miscellaneous changes here and there too. The API of liblzma has got many changes and still some more will be done soon. While most of the code has been updated, some things are not fixed (the command line tool will choke with invalid filter chain, if nothing else). Subblock filter is somewhat broken for now. It will be updated once the encoded format of the Subblock filter has been decided.
2008-01-19	Revised the Delta filter implementation. The initialization	Lasse Collin	1	-0/+97
	function is still shared between encoder and decoder, but the actual coding is in separate files for encoder and decoder. There are now separate functions for the actual delta calculation depending on if Delta is the last filter in the chain or not. If it is the last, the new code copies the data from input to output buffer and does the delta calculation at the same time. The old code first copied the data, then did the delta in the target buffer, which required reading through the data twice. Support for LZMA_SYNC_FLUSH was added to the Delta encoder. This doesn't change anything in the file format.