laziness, impatience, and hubris | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
It doesn't say "Wide character". Specific error message aside, Perl should never treat a number as a 'wide character' without explicit notification from the programmer that that is his intent.
I've already pointed out the documentation is wrong. No! You didn't. Nowhere prior to this post anywhere in this thread. There is no such thing as Unicode number 0x20000, yet So, the documentation is wrong! And the implementation is (silently) wrong! That pretty much covers everything. Unicode support in perl is broken. In Perl, a character is a number in 0 to UVMAX. And that bullshit is exactly why it is so broken. Because &^*&% like you will keep on conflating 'numbers' with 'characters'.
Unicode support in Perl is broken. And until people like you stop pretending that it isn't it will stay that way. Indeed, until those that do, stop trying to pretend that you can transparently handle the abortion that is Unicode, whether retro-fitting an existing language or implementing a new one, the longer it will be before we can evolve some sane semantics for handling MBCSs. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.
In reply to Re^5: Simplest Possible Way To Disable Unicode
by BrowserUk
|
|