I'm looking for suggestions or thoughts on the best way of handling this, as it isn't something I've personally run into, and I haven't been able to find much regarding it.
I've come across a module in CPAN that I really like, however it's written in as a very procedural module, even though it seems like a great candidate for OO to me. Additionally, it would integrate much cleaner into some other stuff I'm doing if it were an OO module.
I'm willing to do the work to write an OO version of the module. My question is, what is the best way to go about this? Specifically, I'd love to hear thoughts and suggestions on:
- Should I contact the author of the existing module and try to get the OO interface integrated into the existing package?
- Is it better to just create a totally separate module? Looking at the code for the existing module, it may be difficult to implement it as a wrapper around the existing module, so it would possibly entail duplicating the functionality, and tracking any enhancements or changes made between the two.
- If the best solution is a separate module, what is the best way to name it? Match the existing module and add an OO suffix (Foo::Bar::OO or Foo::BarOO)? Or something else?
Any other suggestions, thoughts, or tips would be great appreciated.