Newsgroups: perl.perl6.internals
Path: controlnews3.google.com!news1.google.com!newsfeed.stanford.edu!nntp.perl.org
Return-Path: <a...@ajs.com>
Mailing-List: contact perl6-internals-h...@perl.org; run by ezmlm
Delivered-To: mailing list perl6-intern...@perl.org
Received: (qmail 38574 invoked from network); 30 Apr 2004 15:32:53 -0000
Received: from x1.develooper.com (63.251.223.170)
  by onion.develooper.com with SMTP; 30 Apr 2004 15:32:53 -0000
Received: (qmail 14088 invoked by uid 225); 30 Apr 2004 15:32:53 -0000
Delivered-To: perl6-intern...@perl.org
Received: (qmail 14083 invoked by alias); 30 Apr 2004 15:32:53 -0000
X-Spam-Status: No, hits=0.0 required=7.0
	tests=
X-Spam-Check-By: la.mx.develooper.com
Received: from h00036d18ae9c.ne.client2.attbi.com (HELO mail.ajs.com) (24.147.150.110)
  by la.mx.develooper.com (qpsmtpd/0.27.1) with ESMTP; Fri, 30 Apr 2004 08:32:51 -0700
Received: from [192.168.1.233] (ita4fw1.itasoftware.com [63.107.91.99])
	(authenticated bits=0)
	by mail.ajs.com (8.12.8/8.12.8) with ESMTP id i3UFWjAm026581
	(version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO);
	Fri, 30 Apr 2004 11:32:47 -0400
Subject: Re: Bit ops on strings
To: Dan Sugalski <d...@sidhe.org>
Cc: Perl6 Internals List <perl6-intern...@perl.org>
In-Reply-To: <a06100504bcb814d452f6@[10.0.1.3]>
References: <1083253782.4816.1308.camel@pps>
	 <a06100514bcb6e5f0b2f1@[172.24.18.98]> <1083330475.6125.112.camel@wakko>
	 <a06100504bcb814d452f6@[10.0.1.3]>
Content-Type: text/plain
Message-ID: <1083339164.4823.2408.camel@pps>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) 
Date: Fri, 30 Apr 2004 11:32:44 -0400
Content-Transfer-Encoding: 7bit
Received-SPF: pass (mail.ajs.com: 63.107.91.99 is authenticated by a trusted mechanism)
X-Spam-Rating: onion.develooper.com 1.6.2 0/1000/N
Approved: n...@nntp.perl.org
From: a...@ajs.com (Aaron Sherman)

On Fri, 2004-04-30 at 10:42, Dan Sugalski wrote:

> Bitstring operations ought only be valid on binary data, though, 
> unless someone can give me a good reason why we ought to allow 
> bitshifting on Unicode. (And then give me a reasoned argument *how*, 
> too)

100% agree. If you want to play games with any other encoding, you may
proceed to write your own damn code ;-)

-- 
Aaron Sherman <a...@ajs.com>
Senior Systems Engineer and Toolsmith
"It's the sound of a satellite saying, 'get me down!'" -Shriekback