> The entire output buffer must be allocated with a fixed size -- however, callers are able to query the required size
I have not seen a compression library ask for this before. Chunk-at-a-time is not supported? Whole file in RAM? So no-go for memory constrained environments or large files?
This is from the Windows Internals guy? His reputation is pretty good, maybe I am missing something here.
Edit: The code also keeps the input buffer in a global variable. Weird.
I am going to guess he has a very specific use case in mind for this library, like a bootloader or something, where memory management and multiple files are not as important because you decode once and throw out everything shortly after.