On 11/27/2010 4:06 AM, Nicholas Clark wrote: > On Fri, Nov 26, 2010 at 01:03:20PM -0800, Reverend Chip wrote: >> You seriously equate Encode::_utf8_on() with, say, playing around with >> optrees using B? You seriously equate a bad pointer in an SV to a >> misplaced byte in a utf8 string? > Yes. Totally. There are some similarities, but since the ':utf8' layer just slaps the utf8 bit on whatever comes in, the situations are not identical. It's obvious to me that since a regex can die of an assertion due to bad input data, then we might at least want to clue the user in about which regex is dying so he can guard it. Since no one is chiming in to agree with me, I guess I'll just stop. I'm quite disappointed by the apparent lack of concern for the basic usability issues. I'm left with no option but to think of it as evolution in action. > I'd really prefer that it didn't exist at all. I actually use it (properly) in conjunction with utf8::valid to detect and repair double encoding, so I'm very happy it's available. If it weren't, I'd have to write it.Thread Previous | Thread Next