I have mixed feelings about this. On one hand, I find it fascinating that unpack does this and does it so much faster. On the other hand, unless my application is processing huge volumes of text, for the sake of clarity I would opt for the "usual" way.

If I were in a situation where this feature of unpack provided a noticeable performance boost (based on the application and the data being processed) I would add a generous dose of comments explaining what was being accomplished using unpack this way, and why, for the sake (and sanity) of future maintainers. :)

"It's not how hard you work, it's how much you get done."

In reply to Re: Any caveats in using unpack to right-trim? Why isn't it advertised more? by roho
in thread Any caveats in using unpack to right-trim? Why isn't it advertised more? by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.