It is most portable to rely on $/ or "\n". "\r" is incorrect in unix.

It is often helpful to bracket variables in interpolating quotes like so:     print ">${unixfrom}\n"; which allows a construction like "\>${unixfrom}foo\n" in concatenation.

It would be good to print a list of arguments instead of constructing a sequence of print statements.

{ local $, = "\n"; print '>' . $unixfrom, $return_path[$j], $received[$j], $date[$j], $from[$j], $to[$j], $subject[$j], $message_id[$j], $mimeversion[$j], $content_type[$j], $xstatus[$j], $xkeywords[$j], $xuid[$j]; }
That will save some unneeded churning around with interpolation. The print function stringifies its arguments by default, so interpolating quotes are unnecessary.

After Compline,
Zaxo


In reply to Re: Print Question by Zaxo
in thread Print Question by Wako

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.