It all depends on one factor - can you shoehorn your new API into your old one? If you can, then augment the calls to the old parser's functions with simultaneous calls to the new parser's functions. Then, when you're happy, remove the old parser code and let the old parser functions map to the new parser's functions.

Then, you do two more things:

  1. New development goes against the new parser
  2. Maintenance of old development includes changing calls from the old parser to the new parser.

Eventually, you remove all references to the old parser and then you remove it. Usually takes between 6-24 months.

Now, if you can't shoehorn the calls ... well, good luck.

The Perfect is the Enemy of the Good.

In reply to Re: Clean code transition - how? by dragonchild
in thread Clean code transition - how? by shemp

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.