the example there isn't minimal at all
Agreed. I've also no faith in the fidelity of the OPs descriptions.
I'm not sure what happens on windows
It is not at all clear to me that the OP of that thread is using Windows?
I saw a reference somewhere in the Perl documentation saying that with the advent of Unicode support, it has become important to use binmode appropriately even on non-dosish systems. I cannot find that right now, but I do see this:
"For the sake of portability it is a good idea always to use it when appropriate, and never to use it when it isn't appropriate. Also, people can set their I/O to be by default UTF8-encoded Unicode, not bytes."
My point is that this isn't a "windows (only) problem".
I speculate that if you print bytes with the high-bit set, from a no-utf-enabled instance of perl, run from a utf-enabled shell, this situation can arise. Regardless of the OS you happen to be running on.
In reply to Re^4: Standard handles inherited from a utf-8 enabled shell
by BrowserUk
in thread Standard handles inherited from a utf-8 enabled shell
by BrowserUk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |