hey all

I have written a script that parses data from a delimited text file. The script works fine, except doesn't deal well with EOL characters from different OS's (i'm stuck in win32 for the purposes of this script).

Anybody have a code snippet that will detect what the EOL char of the file is, and set $/ accordingly? I've tried various regexps using things like 

if ($_ =~ /\r\n/) { $os = "win"; $/ = "\r\n"; }
if ($_ =~ /[^\r]/ && $_ =~ /\n/) { $os = "unix"; $/ = "\n"; }
if ($_ =~ /[^\n]/ && $_ =~ /\r/) {$os = "mac"; $/ = "\r"; }

[download]

but they don't seem to work for me. Do those look right? Does my problem lie elsewhere in the code? Is there a better way, that doesn't involve checking the EOL every iteration of the loop? (the above code is below the 

while(<FILE>) {

[download]
line ). Any help would be appreciated.

--steve

In reply to mac win and unix EOL chars, $/ question by daemonchild

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.