Bill Janssen wrote: > Nice idea, but it would have been a tad more true to the origin of the > names if "stdin", "stderr", and "stdout" were binary (as the re-use of > those fine names automatically implies to anyone who knows what > they're doing)
No, the names only imply that to Unix users who are ignorant of the correct way to use the C stdio library portably. Right from the beginning, binary mode was an option, and if you didn't ask for it, you got text mode. The same thing applies to stdin/out/err. Anyone using them to handle binary data is and was writing non-portable code. -- Greg Ewing, Computer Science Dept, +--------------------------------------+ University of Canterbury, | Carpe post meridiem! | Christchurch, New Zealand | (I'm not a morning person.) | [EMAIL PROTECTED] +--------------------------------------+ _______________________________________________ Python-3000 mailing list [email protected] http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
