One group where I worked did such a script, to push a bunch of 'csh' scripts into the new Millennium. We wrote a simplistic mechanical translator. The scripts were a bunch of cut-and-paste monstrosities, and the results were just as cruddy. Don't expect human-readable, maintainable results.

One word of advice, anything that requires punting on the translator side should at least KNOW that it requires punting. Output a comment with '#REVIEW:' next to any surely-incomplete translated statements, for example. Then you have a little bit less work to do in hunting down the worst problems with the translated scripts.

The rest of the problems will lurk in obscurity forever.

--
[ e d @ h a l l e y . c c ]

In reply to Re: RFC: UNIX shell to Perl converter by halley
in thread RFC: UNIX shell to Perl converter by cdarke

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.