Re: File coding

AJH> Why is compilation of file-coding.c an option? I'd like it to be AJH> a non-optional, for all sorts of reasons - but in particular AJH> because my encode/decode stuff will otherwise have to include AJH> lots of #ifdef FILE_CODING's. I also think that it would be AJH> better to have it enabled on ordinary UNIX XEmacs, because then AJH> UNIX people won't break DOS, Windows or Mac text files for users AJH> of other less capable software. The main reason is that without FILE_CODING, you get back to that happy land of one-byte == one-char, and files read in can be written out again with absolute certainly that nothing has changed. Perhaps in theory FILE_CODING can be made completely safe, but I think today it is not yet perceived to be (think of editing a binary file). Martin