See Slices.

Also, it's faster than assigning the keys one by one, as the loop runs in C rather than Perl.

#!/usr/bin/perl
use warnings;
use strict;

my @keys = 'a' .. 'z';

sub one_by_one {
    my %hash;
    undef $hash{$_} for @keys;
}

sub slice {
    my %hash;
    @hash{@keys} = ();
}

use Benchmark qw{ cmpthese };
cmpthese(-3, {
    one_by_one => \&one_by_one,
    slice      => \&slice,
});

__END__
               Rate one_by_one      slice
one_by_one 267946/s         --       -25%
slice      359541/s        34%         --

[download]

map{substr$_->[0],$_->[1]||0,1}[\*||{},3],[[]],[ref qr-1,-,-1],[{}],[sub{}^*ARGV,3]

In reply to Re: Hash Curious by choroba
in thread Hash Curious by cadphile

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.