in reply to Re^2: Trying to determine the output length of a Unicode string
in thread Trying to determine the output length of a Unicode string

What "existing solution"? And why isn't length_in_grapheme_clusters() sufficient?

Once again, it's obvious you're making some point, the thrust of which is undoubtedly that I'm wrong about something I wrote, but you're making it too laconically for me to get it. I have no idea what you're saying.

By the way, the version of length_in_grapheme_clusters() I used in my Perl script is attributable to Tom Christiansen. I borrowed it from a PerlMonks post of his. To me, it's better because it makes the operation plainly clear. Your version is tricky and obfuscated, and seemingly weirdly dependent on context. To be honest, I don't understand how it works. To learn how it works, I'd have to read the Perl documentation.

Replies are listed 'Best First'.
Re^4: Trying to determine the output length of a Unicode string
by ikegami (Patriarch) on Sep 26, 2011 at 19:37 UTC

    What "existing solution"?

    See Re: Trying to determine the output length of a Unicode string

    And why isn't length_in_grapheme_clusters() sufficient?

    See Re: Trying to determine the output length of a Unicode string

    I used in my Perl script is attributable to Tom Christiansen.

    Then you should find his comments about Text::Wrap as they are pertinent here. Maybe it was on the Perl5 Porters mailing list (which is archived).

    To be honest, I don't understand how it works

    Most people will say the same about Perl, map, etc, but that's a stupid reason not to use Perl, map, etc. Especially where performance matters, which is likely for this function.

    What I used: ()= returns the length of the list returned by the expression that follows (when used in scalar context).

    How it works: List assignmemt in scalar context returns the number of elements to which the RHS evaluated.

    Your version is tricky and obfuscated

    It's actually very straightforward. There's nothing hidden, it uses well known idioms, and it require only the lowest mental load (only need to remember one value at a time).

    I'd have to read the Perl documentation.

    Really? I use list assignment in scalar context countless times a day. More often than the match operator, I dare say.

    Your implication that someone needs to read the docs for that, but not for \X and capture-less m/.../g is unconvincing.

[reply]
[d/l]
[select]

      You just changed your version of length_in_grapheme_clusters() to be more like Tom Christiansen's. I told you I thought your version was "weirdly dependent on context." It was. Now it's not because you changed it to be more like the one you disparaged earlier.

      I had tested your original, uncorrected version of length_in_grapheme_clusters() in my Perl script and got results I didn't understand when I called the function in list context instead of scalar context.

[reply]
[d/l]
[select]

        I thought your version was "weirdly dependent on context." It was.

        So what? I never said it wasn't.

        I had tested your original, uncorrected version of length_in_grapheme_clusters() in my Perl script and got results I didn't understand when I called the function in list context instead of scalar context.

        Again, so what? You said far more than that, and I responded to the rest of what you said.

        Now it's not because you changed it to be more like the one you disparaged earlier.

        No, I took no steps closer to reintroducing the silly loop.

[reply]

In Section Seekers of Perl Wisdom