Front page | perl.perl5.porters |
Postings from August 2011
On 07/28/2011 09:38 PM, Karl Williamson wrote: > No one has objected to my proposal to go ahead and remove this > problematic feature in 5.16, as planned and documented in 5.14. > > The question is what documentation about it to retain? The 5.14 docs > added significant detail on the problems and issues with this feature. > > http://bit.ly/pwkTR7 > > There was a discussion in p5p on what to do about documenting removed > features, but I can't seem to find it. I do remember that there were > some people who thought that the documentation should be retained. But I > wonder what to do in this case where the feature is being removed > because of significant inadequacies in it, such as not following scoping > rules, etc. > I haven't seen any response to this. Are there any objections to replacing the entire lengthy section in perlunicode.pod with: =head2 User-Defined Case Mappings (for serious hackers only) B<This feature has been removed as of Perl 5.16.> The CPAN module L<Unicode::Casing> provides better functionality without the drawbacks that this feature had. If you are using a Perl earlier than 5.16, this feature was most fully documented in the 5.14 version of this pod: L<https://github.com/mirrors/perl/blob/v5.14.0/pod/perlunicode.pod#User-Defined_Case_Mappings_(for_serious_hackers_only)>Thread Previous | Thread Next