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


In reply to Re: mod_perl and forwarding legacy functions to a global object by dragonchild
in thread mod_perl and forwarding legacy functions to a global object by elusion

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":