On Thursday 17 May 2007 6:23 pm, Bert Freudenberg wrote:
The first case should not fail silently. The error is on purpose (though it might be more meaningful).
True. Gzip files always begin with 0x1f and 0x8b, but this pre-condition is not satisfied by all senders, so there must be a way to inform them about the error.
It did seem weird that CodeLoader>>installSourceFile: aStream .. contents _ aStream ascii upToEnd unzipped. treats first argument as a *.st and then falls back to *.gz. Gzip files are easier to detect than *.st, so shouldn't the order be the other way around?
BTW, is an empty file a valid *.st file (as a trivial case, of course)? filein and change browser handle it gracefully.
Regards .. Subbu