JC> There is one proviso to that: though never says so explicitly, for
 JC> I/O to work correctly (specifically for EOF to be unique from any
 JC> input that could have been read from the file) the range of int
 JC> has to be greater than (not equal to) the range for char.

This  rarely happens.  often EOF is defined as -1  and when char is signed
the two overlap regardless of the size of the two quantities.

if you see EOF in an input char you should check the stream (or fh) explicitly.
using feof() (or eof())

 JC> IOW, if there are 64 bits in the value representation of a char, then
 JC> there had better be at least 65 bits in an int, or the I/O model no
 JC> longer works

that doesn't work with dos where char is 8 and int 16 (or 32)

  -=> Bye <=-

---