From 8b4b30c5d389983c3df51b7ff3b38e5608c7c2e2 Mon Sep 17 00:00:00 2001 From: Karl Williamson Date: Sat, 3 Aug 2019 09:17:43 -0600 Subject: [PATCH] perlapi: 5.30 promise not met; change to 5.32 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit We delayed this change, but I forgot to change this documentation Signed-off-by: Petr Písař --- handy.h | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/handy.h b/handy.h index 24c028a638..2dfbc86125 100644 --- a/handy.h +++ b/handy.h @@ -609,13 +609,13 @@ future releases. Variant C_utf8> is like C_utf8_safe>, but takes just a single parameter, C

, which has the same meaning as the corresponding parameter does in C_utf8_safe>. The function therefore can't check if it is reading -beyond the end of the string. Starting in Perl v5.30, it will take a second +beyond the end of the string. Starting in Perl v5.32, it will take a second parameter, becoming a synonym for C_utf8_safe>. At that time every program that uses it will have to be changed to successfully compile. In the meantime, the first runtime call to C_utf8> from each call point in the program will raise a deprecation warning, enabled by default. You can convert your program now to use C_utf8_safe>, and avoid the warnings, and get an -extra measure of protection, or you can wait until v5.30, when you'll be forced +extra measure of protection, or you can wait until v5.32, when you'll be forced to add the C parameter. Variant C_LC> is like the C_A> and C_L1> variants, but the @@ -649,13 +649,13 @@ future releases. Variant C_LC_utf8> is like C_LC_utf8_safe>, but takes just a single parameter, C

, which has the same meaning as the corresponding parameter does in C_LC_utf8_safe>. The function therefore can't check if it is reading -beyond the end of the string. Starting in Perl v5.30, it will take a second +beyond the end of the string. Starting in Perl v5.32, it will take a second parameter, becoming a synonym for C_LC_utf8_safe>. At that time every program that uses it will have to be changed to successfully compile. In the meantime, the first runtime call to C_LC_utf8> from each call point in the program will raise a deprecation warning, enabled by default. You can convert your program now to use C_LC_utf8_safe>, and avoid the warnings, -and get an extra measure of protection, or you can wait until v5.30, when +and get an extra measure of protection, or you can wait until v5.32, when you'll be forced to add the C parameter. =for apidoc Am|bool|isALPHA|char ch @@ -897,13 +897,13 @@ implementation, and subject to change in future releases. =for apidoc Am|UV|toUPPER_utf8|U8* p|U8* s|STRLEN* lenp This is like C>, but doesn't have the C parameter The function therefore can't check if it is reading -beyond the end of the string. Starting in Perl v5.30, it will take the C +beyond the end of the string. Starting in Perl v5.32, it will take the C parameter, becoming a synonym for C. At that time every program that uses it will have to be changed to successfully compile. In the meantime, the first runtime call to C from each call point in the program will raise a deprecation warning, enabled by default. You can convert your program now to use C, and avoid the warnings, and get an -extra measure of protection, or you can wait until v5.30, when you'll be forced +extra measure of protection, or you can wait until v5.32, when you'll be forced to add the C parameter. =for apidoc Am|U8|toFOLD|U8 ch @@ -944,13 +944,13 @@ implementation, and subject to change in future releases. =for apidoc Am|UV|toFOLD_utf8|U8* p|U8* s|STRLEN* lenp This is like C>, but doesn't have the C parameter The function therefore can't check if it is reading -beyond the end of the string. Starting in Perl v5.30, it will take the C +beyond the end of the string. Starting in Perl v5.32, it will take the C parameter, becoming a synonym for C. At that time every program that uses it will have to be changed to successfully compile. In the meantime, the first runtime call to C from each call point in the program will raise a deprecation warning, enabled by default. You can convert your program now to use C, and avoid the warnings, and get an -extra measure of protection, or you can wait until v5.30, when you'll be forced +extra measure of protection, or you can wait until v5.32, when you'll be forced to add the C parameter. =for apidoc Am|U8|toLOWER|U8 ch @@ -999,13 +999,13 @@ implementation, and subject to change in future releases. =for apidoc Am|UV|toLOWER_utf8|U8* p|U8* s|STRLEN* lenp This is like C>, but doesn't have the C parameter The function therefore can't check if it is reading -beyond the end of the string. Starting in Perl v5.30, it will take the C +beyond the end of the string. Starting in Perl v5.32, it will take the C parameter, becoming a synonym for C. At that time every program that uses it will have to be changed to successfully compile. In the meantime, the first runtime call to C from each call point in the program will raise a deprecation warning, enabled by default. You can convert your program now to use C, and avoid the warnings, and get an -extra measure of protection, or you can wait until v5.30, when you'll be forced +extra measure of protection, or you can wait until v5.32, when you'll be forced to add the C parameter. =for apidoc Am|U8|toTITLE|U8 ch @@ -1047,13 +1047,13 @@ implementation, and subject to change in future releases. =for apidoc Am|UV|toTITLE_utf8|U8* p|U8* s|STRLEN* lenp This is like C>, but doesn't have the C parameter The function therefore can't check if it is reading -beyond the end of the string. Starting in Perl v5.30, it will take the C +beyond the end of the string. Starting in Perl v5.32, it will take the C parameter, becoming a synonym for C. At that time every program that uses it will have to be changed to successfully compile. In the meantime, the first runtime call to C from each call point in the program will raise a deprecation warning, enabled by default. You can convert your program now to use C, and avoid the warnings, and get an -extra measure of protection, or you can wait until v5.30, when you'll be forced +extra measure of protection, or you can wait until v5.32, when you'll be forced to add the C parameter. =cut -- 2.21.0