Hello Antonio, > Resetting the internal flags to a state equivalent to a decoder just after > creation can't work. Suppose the next header has not been yet fed to > LZ_decompress_write. You'll have to switch to a "search" state, then write > data until the header is found. > > Certainly this case deserves its own explicit function, in addition to any > LZ_decompress_reset that we may find useful to implement, but I'm afraid I > can write it until next year.
I assumed that the API client already forwarded its steam to the beginning of the next member, which means that the first bytes written using LZ_decompress_write(decoder, ...) are 'LZIP...'. That's the way I did it for now. Good night, Jacob _______________________________________________ Lzip-bug mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/lzip-bug
