Felipe Gasper <felipe@felipegasper.com> wrote: > Then thereâs utf8::is_utf8(), which, for pure-Perl code, usually means the *opposite* of what it looks like it means. THIS. IS. MADNESS. No one groks it all without investing *significant* effort. I can see how a global rename throughout the internals could be a lot of work, I was going to make the point that in my experience the place where the confusion hits client programmers is "is_utf8". It gets used wrong a lot, to the point where when I see it used I'm not sure what I should think-- is this a code smell, or is this one of the few who really gets what it means (and I'm still not sure I do). Modest proposal: add an alias to is_utf8 to something else, e.g. "is_heavy" (I think I'd prefer "is_modern" but that's not without issues.) Then encourage the use of the new form, and possible deprecate the old one.Thread Previous | Thread Next