Setting $/ to undef causes the next read on any file handle to be done in "slurp" mode -- i.e. everything from the current file offset pointer to the end of file gets pulled in as a single scalar value. Usually, this is done before the first read on a file handle, so the full content of the file comes in as a scalar on one read operation.

Setting $/ to something and then setting it back to its previous value, without doing any file input between those two settings, has no effect on anything -- so those two lines assigning to $/ within your while loop are pointless.

In scripts that use modules or that manage more than one input file, it is best to localize changes to $/ within the smallest essential code block, like this: 

my $filecontents;

if ( open( FILE, "whatever" ))
{
    local $/;  # this sets $/ locally to undef within this block
    $filecontents = <FILE>;
    close FILE;
} else {
    die "whatever: $!";
}
# all data from "whatever" is now contained in $filecontents
# and $/ is now back to its previous value

[download]
There are other idioms involving "do { ... }", which would be easy to find here with SuperSearch.

(updated code snippet to fix missing paren)

In reply to Re: $/ is playing havoc with my script. by graff
in thread $/ is playing havoc with my script. by blackadder

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.