On Fri, 21 Jul 2017 02:02:08 -0700, xsawyerx@gmail.com wrote: > +1 > > (Except "$a" still appears in the comments next to the lines that now > say "$x". Sorry.) Fixed and applied as e423fa83496ce7d83b137bd7f0852864b6073b36, 01c3fbbc0d1b54bb0dd6fdc0abed7854e62c6717, ee329aefb9c0bfcee0e6cc41dcd6eb8b03206f30 and 0397beb0d12565d70e168bfea7376e2612a6748a. Is there anything else we should do to avoid mis-use of these functions? I previously said: > > > Using this flag to decide whether a string should be treated as > > > already encoded bytes or characters is wrong, this should be > > > decided as part of the interface of your function. > > which could perhaps use some expansion in perlunicode. > perlunitut covers this reasonably well. I'm referring to "I/O flow (the actual 5 minute tutorial)", should this be expanded elsewhere? I don't think it should be expanded in perlunitut. Tony --- via perlbug: queue: perl5 status: open https://rt.perl.org/Ticket/Display.html?id=131685Thread Previous | Thread Next