Re: Best Practices for creating an OO version of an existing CPAN module?

in reply to Best Practices for creating an OO version of an existing CPAN module?

Should I contact the author of the existing module and try to get the OO interface integrated into the existing package?

Better check with the author first, after that you can decide on implementing the separate module.

Comment on Re: Best Practices for creating an OO version of an existing CPAN module?

Replies are listed 'Best First'.
Re^2: Best Practices for creating an OO version of an existing CPAN module? by topher (Scribe) on Feb 25, 2013 at 17:33 UTC
So you are of the opinion that the best option is to try to include both interfaces in the same module? Note: I'm not disagreeing with you, just trying to make sure I understand. I've seen a couple of modules that supply both a procedural and OO interface in the same module, and a bunch that implement them separately. I'm trying to figure out if there's any benefit or detriment to one over the other.	[reply]

Replies are listed 'Best First'.

Re^2: Best Practices for creating an OO version of an existing CPAN module?
by topher (Scribe) on Feb 25, 2013 at 17:33 UTC

So you are of the opinion that the best option is to try to include both interfaces in the same module?

Note: I'm not disagreeing with you, just trying to make sure I understand. I've seen a couple of modules that supply both a procedural and OO interface in the same module, and a bunch that implement them separately. I'm trying to figure out if there's any benefit or detriment to one over the other.

[reply]

In Section Seekers of Perl Wisdom