You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This compressor is awesome, so thanks for sharing your code. :)
Apologies in advance if this is not the right place to ask.
Is there any reason why you use 2 bytes for tags instead of 1?
I implemented the depacker in 96 bytes, but was thinking it could be smaller (not much of course) if smaller tags used.
The text was updated successfully, but these errors were encountered:
I guess at the time because I used 8-bit tags in aPLib, and some of the other compression libraries at the time were moving to 32-bit tags to improve speed. I wanted something that could still be implemented in little code on 16-bit x86, so 16-bit tags were the compromise.
One nice thing about using 16 rather than 8 bits is that because the literal bytes are interleaved with the tag bits, it is not possible to "peek" many bits ahead, but having up to 16 bits allowed sometimes using the lookup table in the decoder for speed.
Hello,
This compressor is awesome, so thanks for sharing your code. :)
Apologies in advance if this is not the right place to ask.
Is there any reason why you use 2 bytes for tags instead of 1?
I implemented the depacker in 96 bytes, but was thinking it could be smaller (not much of course) if smaller tags used.
The text was updated successfully, but these errors were encountered: