Re: check process state before accessing coding_stream (fix PR#1061)

Ben> If you want to be more adventurous, I'd suggest some more Ben> general changes to make these type errors clearer. I've Ben> always hated these. For example: I've always hated them, too. But I have on occasion written code to parse the *Messages* buffer for these error messages; somebody may actually haved saved some code that does that. Somehow this should be configurable. BLUE SKY ALERT: Some day these things should be gettext-ized anyway. Lots of Japanese don't understand that message no matter how good the English is ;-) We should think about how the message catalogs should be done; can we really use gettext? Do we want multilingual capabilities (same process using multiple languages---I have been in the situation of trying to figure out Japanese errors from Mule code and would love to have that capability when the catalogs are available, but it's probably hard to do). -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."