I suspect you will do no worse letting Perl handle the buffering for you:
$/ = \8; # Read 8-byte records. Behind the scenes, Perl will do buffer
+ing of reads.
$out_buffer .= blowfishify($_) while <INFILE>;
print OUTFILE $out_buffer;
Alternatively, you could (with a sufficiently modern Perl) read from your buffer as if it were a filehandle, using the same
$/ = \8 trick.
open BUF, '<', \$buffer or die "$!: Could not open buffer\n";
$/ = \8;
$out_buffer .= blowfishify($_) while <INFILE>;
print OUTFILE $out_buffer;
They're tidier ways of doing what you want, but you'd have to try them to see whether they buy or lose you any efficiency. My guess is that the I/O isn't going to be the bottleneck, anyway; the encryption is.
Caution: Contents may have been coded under pressure.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.