while is 19% faster! Well, for small files. For big files, it's probably the same speed, but more readable.

use Benchmark qw( cmpthese ); cmpthese(-3, { 'for' => sub { open(my $fh_in, '<', $0) or die("Unable to open input file: $!\n"); my $infile_num_chunks = int((-s $fh_in) / 8); for ($chunk_counter = 0; $chunk_counter < $infile_num_chunks +1; + ++$chunk_counter) { read($fh_in, my $data, 8); # ... } # ... 1; }, 'while' => sub { open(my $fh_in, '<', $0) or die("Unable to open input file: $!\n"); while (read($fh_in, my $data, 8) == 8) { # ... } # ... 1; }, });
Rate for while for 1068/s -- -16% while 1273/s 19% --

In reply to Re^7: Fast parsing for cypher block chaining by ikegami
in thread Fast parsing for cypher block chaining by fluffyvoidwarrior

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.