I don't have an answer -- sorry -- but have you tried this:
perldoc perlport
It's pretty comprehensive (maybe even paranoid, which is not a bad thing in this context). Apart from that, you would at least need to actually put your scripts onto a Windows box that has the suitable version of Perl installed, fire up a command-line prompt window, have a windows port of bash on hand, just to make it easier, and do:
for i in *.pl; do perl -cw $i > $i.chk 2>&1 done
Get windows ports of other useful things, like grep and sort (or roll your own perl equivalents, since this is typically not much harder than locating the ported code on the web and installing it), in order to go over the *.chk files for common issues.

update: Of course, if you use CPAN modules that aren't part of the core perl distribution, that can put a slight damper on portability. In this case, part of your question could be "is there an easy way to distribute portable code so that when recipients install it, it automatically checks for modules it needs and downloads them from CPAN when necessary?" That's a damn good question, and I'm sure someone can suggest a good answer... (I'll check back to look for that.)


In reply to Re: Compatability parser? by graff
in thread Compatability parser? by SpaceAce

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.