The distinctions among read, sysread, and getc are useful, but any of them serve to point out the issue in the original node. I used read specifically because it is more flexible than getc and does interact properly with buffering if there is any. That may be preferable in some situations, but sysread may be preferable if bypassing buffers is desired as a rule.
As an aside, although there is for perl 5.10.1 and 5.12.0 a note at the bottom of the entry for sysread in the perldocs about UTF and characters, the documentation for read is clearer at a glance about handling characters and not just bytes. That's not anything against the function, and it will probably be fixed in the docs at some point. It's worth noting if you're pointing the function out to people in the meantime, though, because you might want to mention that note stuck at the bottom of the entry.
In reply to Re^5: Nested line buffered output
by mr_mischief
in thread Nested line buffered output
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |