PREV INDEX NEXT

Author: Unknown
Subject: Storing string table LZW
Date: Sunday, 11 Oct 2020, 17:08:13

In most scenarios, is it true that COMPRESS and ENCODE have different data structures for storing the string table (e.g., hash table for COMPRESS and array of (P,K) indexed by code # for ENCODE)?

As a loosely related aside, if I understand correctly, having two different structures will not break the synchronization rule of a compression scheme, since the messages read and sent could still be the same, correct?
PREV INDEX NEXT