It seems to me you've got 3 options there:
1. auto-translate;
con: GIGO ie crud shell input => crud Perl output.
pro: quick/low effort
2. Hand code new Perl modules as you go.
con: Takes a while, same cruddy architecture as original
pro: you'll get good, maintainable Perl that does logging etc. Also means you can replace shell files gradually, instead of the big bang approach.
3. Design a new/better ctrl system in Perl from scratch.
pro: Gives you better code and more integrated approach.
con: more effort upfront & big bang approach
I once had to do a FORTRAN to C job (Y2K) and we originally tried option (1.), but I ended up doing a fair bit of (2.) to make it work properly.
A straight option (2.) approach might have been quicker in the long run, otherwise you end up with weird looking code due to the auto-converter.
HTH
Cheers
Chris
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.