I have a package called PDF::OCR which was written a while back. The module worked well for my purposes, I wanted other people to have access. I makde sure to note that it was a development version.

Later on when I had developed the code better- simplified the package- I realized that api was not compatible with the old PDF::OCR.

A number of people were using PDF::OCR, and I didn't want to release a version that would break their code. So I released PDF::OCR2, a better tool, that does the same work, better- with a differnt api.

Since, I have received various questions, complaints, inquiries as to why there is a PDF::OCR and a PDF::OCR2.
I would like to do the right thing, and release a new version of PDF::OCR with the updates.
It's going to break the code of anyone interfacing with the old version.

Should I keep things the way they are, label PDF::OCR as deprecated, or have some discipline and no mercy- and just update PDF::OCR.

I feel a little retarded that the api did not stay the same. I'm sorry. It was just a complex procedure, and I ended up separating the code into smaller and properly manageable modules.

In reply to Update module and break api, or change namespace by leocharre

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.