In case the many replies using this approach have not made it clear, you can get more information about $/ from running "perldoc perlvar", and scanning down till you see this one described (with the long name "$INPUT_RECORD_SEPARATOR"). Normally -- i.e. by default -- $/ = "\n" (which in reality would be "\r\n" on MS-DOS/Windows systems, "\r" on "Classic" macs, and truly "\n" on unixes).

It's the character pattern that is removed from the end of a string when you "chomp" the string, and it is the pattern that the diamond operator looks for when reading data from a file handle into a scalar, to know when to stop. If set to "undef", it causes a single read operation to absorb the entire file and assign it all to a single scalar.


In reply to Re: Re: Re: Scanning a text file by graff
in thread Scanning a text file by Anonymous Monk

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.