From: Nicholas Clark Date: Fri, 14 Jan 2005 09:55:16 +0000 (+0000) Subject: Improve documentation for sv_catpvf, to note that pattern's UTF-8ness X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=cdd94ca776dceea28cef3714a8bc6d873614b2bf;p=p5sagit%2Fp5-mst-13.2.git Improve documentation for sv_catpvf, to note that pattern's UTF-8ness is taken from the SV's UTF-8ness p4raw-id: //depot/perl@23800 --- diff --git a/pod/perlapi.pod b/pod/perlapi.pod index 3939098..a1ddb13 100644 --- a/pod/perlapi.pod +++ b/pod/perlapi.pod @@ -3949,7 +3949,8 @@ output to an SV. If the appended data contains "wide" characters (including, but not limited to, SVs with a UTF-8 PV formatted with %s, and characters >255 formatted with %c), the original SV might get upgraded to UTF-8. Handles 'get' magic, but not 'set' magic. See -C. +C. If the original SV was UTF-8, the pattern should be +valid UTF-8; if the original SV was bytes, the pattern should be too. void sv_catpvf(SV* sv, const char* pat, ...) diff --git a/sv.c b/sv.c index e9e0eca..e781904 100644 --- a/sv.c +++ b/sv.c @@ -9008,7 +9008,8 @@ output to an SV. If the appended data contains "wide" characters (including, but not limited to, SVs with a UTF-8 PV formatted with %s, and characters >255 formatted with %c), the original SV might get upgraded to UTF-8. Handles 'get' magic, but not 'set' magic. See -C. +C. If the original SV was UTF-8, the pattern should be +valid UTF-8; if the original SV was bytes, the pattern should be too. =cut */