Sigh. One of these days, I'll learn to proofread and test code before posting to PM, even on things that I shouldn't have to. In this purticular case, I did test the code... in as much as I tested if it ran, but not if it gave the correct results. I never did a mental sanity check on the code from the original post, or printed the output of either method.

As to the $& problems, I did know about them, but figured that they were too advanced for the poster, and there's a better way to do it anyway. I knew about the leekage of badness, figured it would effect my benchmarks, and that it wouldn't be a major effect. Seems I underestimated how bad it was.

Confession: It does an Immortal Body good.

In reply to Re: Unfortunately benchmarking things with $& isn't easy... by theorbtwo
in thread Obtaining server name from UNC path by blackadder

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.