Tweak the definition of the bit complement on UTF-8 data:
authorYitzchak Scott-Thoennes <sthoenna@efn.org>
Fri, 10 Nov 2000 09:47:15 +0000 (01:47 -0800)
committerJarkko Hietaniemi <jhi@iki.fi>
Mon, 13 Nov 2000 04:05:07 +0000 (04:05 +0000)
commita1ca4561f20dbf547f57d39a690790cbe33210da
tree83f9af82cb7a2699ca5ca248e9907ac52b3924a8
parentd26ab924bbea5dd5379307deb59c11af3692350b
Tweak the definition of the bit complement on UTF-8 data:
if none of the characters in the string are > 0xff,
the result is a complemented byte string, not a (UTF-8)
char string.  Based on the summary in

Subject: Re: [ID 20000918.005] ~ on wide chars
Message-ID: <jSDD6gzkgi/T092yn@efn.org>

This should give us the maximum backward (pre-char string)
compatibility and utf8 compatibility.  The other alternative
would be to limit the bit complement to be always byte only,
taking the least significant byte of the chars.

p4raw-id: //depot/perl@7665
doop.c
pod/perlunicode.pod
pp.c
t/op/bop.t