I'm one of those rather peculiar programmers who would finds excuses to write library functions 8-), so I can understand why you write a module.

I tend to like your 3d option (complete re-write, keep the old interface for the existing code, and make the new interface available for new code) the most attactive from a technical point of view, and your second option most from an overall point of view. I really do not like either of the last two options, which (in my opinion) are really different ways of doing the same thing.

Added "attractive" so the sentence actually makes sense.

emc

In reply to Re: How to avoid (or handle) module interface changes by swampyankee
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.