It looks to me like the major case where the benchmark straight-out lies (well, where you, the speaker, presumably lie about what it's saying) is that the first snippet is in list context, and the second is in void context. Simply adding my @results = before the initial (in lexical order; final in execution order) map would fix that, and still have it fit on your slide (assuming your slide uses a monospaced font). You could probably even write it on a sepperate line and still have it fit on the slide.
The rest of the changes make the benchmark more useful, perhaps, but they do not unfairly favor one over the other -- the most important type of error to avoid in any benchmark. (The reason, for example, that polls should rotate the options -- there's a significant bias amongst voters for the first option listed on a form.)
Warning: Unless otherwise stated, code is untested. Do not use without understanding. Code is posted in the hopes it is useful, but without warranty. All copyrights are relinquished into the public domain unless otherwise stated. I am not an angel. I am capable of error, and err on a fairly regular basis. If I made a mistake, please let me know (such as by replying to this node).
Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
Want more info? How to link or
or How to display code and escape characters
are good places to start.