I soon noticed that it was using local $/=undef. Which I gathered is generally frowned upon.
Eh? That's news to me.

Anyway, I see you're trying to read 64 bytes at a time, so you might think of setting $/ to a ref to a scalar containing the value 64. This will work: 

local $/ = \64;

[download]
as will 
my $length = 64;
local $/ = \$length;

[download]

After that, you can just read from the file with <HANDLE>, but I recommend calling binmode on the handle first, unless, maybe, you're absolutely sure you will only ever run this on Unix-like systems.

But I'd still do it anyway.

In reply to Re: Avoid using local $/=undef? by bart
in thread Avoid using local $/=undef? by irDanR

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.