Front page | perl.perl5.porters |
Postings from July 2017
On 4 July 2017 at 09:19, <pali@cpan.org> wrote: > On Tuesday 04 July 2017 10:38:26 Tony Cook wrote: >> But it does deprecate the old names, which is an issue, I can't >> imagine us removing these functions. > > Warning can be removed from patch. It is just question how you decide. > Also functions stay there, but we can instruct people via documentation > to use new functions for a new code... Again it is question if you call > it deprecation or aliasing. In any case functions are not going to be > deleted, so in final case it does not matter for old code. > > And for old code can be defined this function easily: > > *new_name = *old_name; > > Reason for this patch series is: > * document those utf8:: functions > * allow developers to call those functions via non-cryptic names I dont mind adding new aliases for these functions, I object to your proposal to put them in Internals however; I think that they should go in 'scalar', which we decided at the last PerlQA is the designated place for functions that operate on scalars. scalar::is_unicode_string() scalar::is_binary_string() I don't like the wide-storage thing, (although I admit i think it better than "is_utf8"), a latin1 string in utf8 does not use wide-storage, and the unicode flag has significance beyond the storage format; utf8-on strings get unicode semantics in case insensitive operations. cheers, Yves Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"Thread Previous | Thread Next