The general question of how to provide a legacy API to a modern system is pretty easy to answer - you'll want to look at singletons for most of your work. The $64K issue is how to provide the state your objects need so that they do what they need to do. Generally, one would hope that the mapping between the parameters passed into Legacy::Ugly_Sub_Name() and New::pretty_method() is extremely close. The only issue I've run into doing this is when the Legacy package maintained a bunch of state using file-scoped globals. If that's the case, I'd look at some sort of external datastore, like a RDBMS, especially if you're in a persistent environment.
As for specifics, the previous posters got you covered, I think.
We are the carpenters and bricklayers of the Information Age.
Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose
I shouldn't have to say this, but any code, unless otherwise stated, is untested
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, 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, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||