Hmph, this could be changed back.

I made this change while getting decompression to work with the changes. The general problem is that no module object exists before the decompression code has actually decompressed it, so the functions were converted to globals for the decompression code to use, and once the module has loaded the shell can overwrite Module.setStatus with the global setStatus;

However, after making this change I realized I had to provide a fake Module for shell to use (as it's expecting Module to exist in any script tag following the module script tag), so this can be reverted.

Out of curiosity, is there a particular reason this is offered with emscripten? Compressing / decompressing content seems more the job of the browser / server.