From 30a15352eb3f11a226bd42ec93797b1e778f6e9f Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Sun, 4 May 2014 18:58:51 -0600 Subject: perlapi: Clarify some instances where NUL is or isn't permitted Some functions that take a string/length pair can have embedded NULs and don't have to be NUL terminated; others are the opposite. This adds text to clarify the issue. --- sv.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) (limited to 'sv.h') diff --git a/sv.h b/sv.h index 003112c48d..abcfbb63ae 100644 --- a/sv.h +++ b/sv.h @@ -2163,7 +2163,8 @@ struct clone_params { /* =for apidoc Am|SV*|newSVpvn_utf8|NULLOK const char* s|STRLEN len|U32 utf8 -Creates a new SV and copies a string into it. If utf8 is true, calls +Creates a new SV and copies a string (which may contain C (C<\0>) +characters) into it. If utf8 is true, calls C on the new SV. Implemented as a wrapper around C. =cut -- cgit v1.2.1