Don’t use two-argument open. It’s dangerous.

And if you do, at least don’t omit the mode as well. That’s doubly dangerous.

Otherwise, there is opportunity for someone to do mischief, should any user input ever get close to your $filename. Stay away. Be explicit. Use three-argument open and always fasten your seatbelt.

As far as slurping is concerned, as others have mentioned, you want to explicitly undefine $/, so that Perl won’t waste effort splitting the input into lines, only to then waste more effort gluing them back together. I tend to do this using a do {} block, much like those which tinita posted, because I rarely need to slurp files in more than one place in my code.

Makeshifts last the longest.

In reply to Re: slurp mode by Aristotle
in thread slurp mode by szabgab

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.