Any good response to your post will require significantly more information.

Here are a few questions to start with:

  1. How much code? Are we talking less than a few thousand lines, 20,000+, or somewhere inbetween?
  2. What type of code? Is the language still in active development?
  3. What are you skills? Are you capable of making reliable modifications to the code? Do you know the language well, or just enough to rename variables?
  4. Who owns the code Does it belong to a company or an individual? Is it open source? How resistant is the company to change?
  5. What is the owner's current focus Have they switched all new development to a different platform and/or language? Are they in the process of migrating any other code from the same eroa over?
  6. What is the purpose of the code Is it for a pacemaker or an mp3 player? What level of quality is required.
  7. How well does the code work? Have many bugs been found in the past? Are there an unresolved known problems? How extensively is it tested/used?
  8. How much other code is dependant on it? Can you change the interface? Is it so obscure that you can't tell what the interface is?
  9. How well is it documented? How much do you know about the code's purpose? The interface? Internal workings?

That's a start anyways. These things are extremely dependant on the details, carefully examine any advice that claims to be a silver bullet.

Best of luck.


In reply to Re: Difficult code (Resolutions) by Anonymous Monk
in thread Difficult code (Resolutions) by xChauncey

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.