I agree with what you have. Portability is the main reason I persuaded our team to use Perl instead of Unix shell and DOS batch jobs. Also, it makes it easier for new team members to learn how to script when they only have to learn Perl (as opposed to DOS batch and Unix KSH). The only KSH script that I have written for production type use is a very basic script and all the commands would be system calls anyway (could have been written in Perl but was just as easy to write in Korn). I have found that with Perl, it was easier to put in pretty solid error handling that is pretty reliable. Lastly, Modules make it easier to have repeatable routines that can be shared from one process to another.
Just my 2 cents :-)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||