Glenn Linderman writes: > But the API could speak Unicode, and do the appropriate translations. > Or in some cases, inappropriate translations.
You've written that kind of thing three or four times by now. As far as I can see, you just don't care about any requirements beyond your own. > Please be specific; just mentioning bit-flicking, or error cases, or bad > encoding sounds terrible, but provides little information as to how it > can be handled via some theoretical bytes interface that cannot be > handled equally as effectively (although perhaps not equally > efficiently) via a transliterated Unicode data stream. I did. You missed it. Reread my example of mixing types. That is not theory, that is Emacs practice. And it's not good practice. _______________________________________________ Python-3000 mailing list Python-3000@python.org http://mail.python.org/mailman/listinfo/python-3000 Unsubscribe: http://mail.python.org/mailman/options/python-3000/archive%40mail-archive.com
