Re: Lstreams, coding and md5 (was: Re: [PATCH] menubar selection in mswindows)

Some time ago, Hrvoje Niksic wrote... |+ | "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp&gt; writes: | | > But if you're actually going to stuff it into a TCP/IP stream via a | > process buffer, you need to use coding-system-for-process-output (or | > whatever the appropriate variable is named). | | OK, this is the crux of your argument, and I see what you mean. | Still, how often does coding-system-for-write differ from | coding-system-for-process-output? If such case is degenerated, then | using a coding-system-for-md5 variable might not be such a bad idea, | because it would be used only very rarely. Why don't you want to use the same coding-system-for-write variable? coding-system-for-process-output and coding-system-for-md5 are only messing things, i.e. I should which one I should bind in a let clause around a call to which function. There must be only one variable for one I/O direction (if we loosely assume that md5 hash is intended to be transmitted, so is a kind of output). If there must be a configure variable which defines a default coding system for md5 hashing, heaven save C code from depending on it, no? Kirill