As Ovid said.

The real beauty of Perl is that you can hack on what ever platform you are most comfortable with and then "port" your code over to another platform and have a 95% chance of it working right the first time. (I don't say 100%, because I have been bitten more than once by CPAN modules that I forgot I installed on the dev-box. But, since they are on CPAN, that is easily remedied.)

That said, working on one of the *nix flavors is my personal preference, particularly if I am going to be building and software from source. (But then, I am old-fashioned, after all.) I always get into snarling contests when I start working with compilers/linkers/nmake under a Windows OS.

----
I Go Back to Sleep, Now.

OGB


In reply to Re: Suggested OS for Perl Hacking by Old_Gray_Bear
in thread Suggested OS for Perl Hacking by geekondemand

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.