On Tue, Jun 18, 2013 at 11:53 AM, demerphq <demerphq@gmail.com> wrote: > > The interface for Perl_croak() and friends do not support UTF8 at all. > They accept only a char* pointer, and have no facility for a UTF8 > flag. Then it can be safely used as neither UTF-8 nor any 8-bit encoding, right? Shouldn't they then, to preserve sanity, treat the char* data as binary and convert all high-bit-set bytes to some ASCII representation (octal escape sequences or whatever)? That would still leak internal representation, but at least it would be an actual internal representation ... EirikThread Previous | Thread Next