Discounting an obsolete build of Perl on an obsolete version of Mac, there's no OS dependency. The only difference is whether the :crlf I/O layer is used or not.

The :crlf layer is used by default on Windows and in environments where it appears in $ENV{PERLIO}. Overriding the default PerlIO layers can avoid it, and the one-argument call to binmode disables it.

With :crlf IO layer absent or disabled
MacPerl*Everything else
\nCRLF
\rLFCR
\012LFLF
\015CRCR
\015\012CR LFCR LF
With :crlf IO layer present and enabled
MacPerl*Everything else
\nN/ACR LF
\rN/ACR
\012N/ACR LF
\015N/ACR
\015\012N/ACR CR LF

MacPerl is an obsolete build of Perl for obsolete Macs. It predates PerlIO.

In reply to Re^2: File I/O question by ikegami
in thread File I/O question by sierpinski

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.