From: Karl Williamson Date: Wed, 7 Mar 2018 19:11:26 +0000 (-0700) Subject: perlapi: Clarifications to Perl_langinfo X-Git-Tag: v5.27.10~52 X-Git-Url: https://perl5.git.perl.org/perl5.git/commitdiff_plain/c3997e39b6a1f4b4b51aa6f192c7d5f1be7d711b perlapi: Clarifications to Perl_langinfo --- diff --git a/locale.c b/locale.c index 85ff971..b90d69f 100644 --- a/locale.c +++ b/locale.c @@ -2322,7 +2322,12 @@ system. It is important to note that when called with an item that is recovered by using C, the buffer from any previous explicit call to C will be overwritten. This means you must save that buffer's -contents if you need to access them after a call to this function. +contents if you need to access them after a call to this function. (But note +that you might not want to be using C directly anyway, because of +issues like the ones listed in the second item of this list (above) for +C and C. You can use the methods given in L to +call L and avoid all the issues, but then you have a hash to +unpack). The details for those items which may deviate from what this emulation returns and what a native C would return are specified in @@ -2337,7 +2342,8 @@ C, you must before the C C<#include>. You can replace your C C<#include> with this one. (Doing it this way keeps out the symbols that plain -C imports into the namespace for code that doesn't need it.) +C would try to import into the namespace for code that doesn't need +it.) The original impetus for C was so that code that needs to find out the current currency symbol, floating point radix character, or digit