You left out the option of your new code living in the same namespace: to extend and wrap and deprecate stuff in one module.

Then you have all your code proximate and can keep your users and push them toward the new code. In your case it seems the pushiness may be tolerable since users will be attracted to the better interface functions. It also leaves you in a good position to refactor and reuse.

Coming up with new names for functionality can be a pain.

Wrappers are a simple way to extend and abstact existing code. I think your point regarding wrappers is valid but I feel that you are viewing them too negatively in this situation.

Be well,
rir

In reply to Re: How to avoid (or handle) module interface changes by rir
in thread How to avoid (or handle) module interface changes by chester

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.