|We don't bite newbies here... much|
Re^4: Character in 'b' format wrapped in unpackby BrowserUk (Pope)
|on Mar 29, 2015 at 20:49 UTC||Need Help??|
I'm sorry to disagree
I guess we'll have to agree to differ; but the fact that Perl allows me to replace an (8-bit) character, in the middle of a string of 8-bit characters, with some (random*) wide character is just broken.
"chr()" is - and rightly should be - intended to serve the (dominant) linguistic sense of "character" (what the perl docs call "character semantics")
To what possible end?
When you do my $thing = chr( 12345 ); what does that "character" represent?
Is a Chinese character? Or Sanskrit? Or Cyrillic?
Is it utf-8; utf16; utf32?
Is it big-endian or little-endian?
What if I append another character to it: $thing .= chr( $i );. What does string contain now? Can Perl ever decide what encoding $thing contains?
And the answer to all of those questions is: it is impossible to ever know. Thus, chr's ability to construct wide characters is entirely useless.
So, you break with clearly defined semantics for undefined and undefinable semantics, for what purpose?
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
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". I'm with torvalds on this
In the absence of evidence, opinion is indistinguishable from prejudice. Agile (and TDD) debunked