That is one option. I tend to prefer, after a few times doing this, to rewrite the app. The number of improvements and bugs fixed tend to outweigh the number of errors.

If you have buggy code that nobody understands then translation may be a better option.

In my case my clients were perfectly happy with their little language and the quality of their codebase. They were not happy with their PDP-11s - which were getting more expensive to maintain every year. So building a new compiler for a new box was the obvious decision. For all I know they're still tweaking their little expert system now.

If we'd gone the translation route then not only would the development time have been longer, the client would have also had to retrain their internal people to use a new language.

Also 20KLOC isn't really that much. When you have organisations with hundreds of programmer years invested in their code you know why they prefer to take compiler development in-house rather than manually convert everything to whatever the current language-of-choice is :-)

The number of improvements and bugs fixed tend to outweigh the number of errors. Granted, I have only worked with relatively young apps and rewriting them after they were implemented by junior developers. *shrugs* YMMV, as with everything

Indeed. Sometimes moving to another language is exactly the right thing to do. Context is everything.

In reply to Re^4: Mission critial code required: I have some code in BASIC and require it to be translated to perl by adrianh
in thread XBASIC to Perl translator: semantical equity by Anonymous Monk

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.