The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 |
Newsgroups: perl.perl6.internals
From: a...@ajs.com (Aaron Sherman)
Date: Sat, 01 May 2004 12:00:05 -0400
Local: Sat, May 1 2004 12:00 pm
Subject: Re: Bit ops on strings
On Sat, 2004-05-01 at 11:26, Jarkko Hietaniemi wrote: As for codepoints outside of \x00-\xff, I vote exception. I don't think there's any other logical choice, but I think it's just an encoding conversion exception, not a special bit-op exception (that's arm-waving, I have not looked at Parrot's exception model yet... miles to go...) > > This means that UTF-8 strings will be handled just fine, and (as I What I meant was that UTF-8 IS going to be represented in a way that > Please don't mix encodings and code points. That strings might be will guarantee you won't get an exception when trying to do bit-ops. All bets are off for many other encodings. While you're right that you might get lucky, that wasn't really the point I was making. Many languages (Perl included, I think) are going to encode strings as UTF-8 by default, and this means that in the general case, we should not expect exceptions to be thrown around any time we do a bit-op and 'A'|'B' will still be 'C' :-) > Of course. But I would expect a horrible flaming death for Well, if you consider a string conversion exception to be horrible > "\x{100}"|+"\x02". flaming death, then I hate to see what you do with a divide-by-zero ;-) None of your response sounds overly scary to me, so I'll start looking --
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
| ||||||||||||||||
