Front page | perl.perl5.porters |
Postings from March 2014
2014-03-27 3:12 GMT+04:00 Karl Williamson <public@khwilliamson.com>: > > locale works a lot better (I anticipate) in 5.20 than before. So, it worked bad before? Than it will be hard to write code compatible with 5.20 and, say, 5.8.8 at same time (that again related to 'ack'-like programs - it's command line program that should work in system perl installed by end users. it's not a web application where programmer can choose perl version) > The problem is that the commit fixed real bugs in code that didn't "use > locale" Thus the quandary. If we go back to 5.18 behavior, those bugs come > back. Who told that it was bug? I saw this behaviour but never thought it is a bug, because there is note in documentation: === While Perl does have extensive ways to input and output in Unicode, and a few other "entry points" like the @ARGV array (which can sometimes be interpreted as UTF-8), there are still many places where Unicode (in some encoding or another) could be given as arguments or received as results, or both, but it is not. === a user reported this as bug because he did not read this. for me it's documented behaviour.Thread Previous | Thread Next