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.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.