in reply to Re^3: Best Practices for creating an OO version of an existing CPAN module?
in thread Best Practices for creating an OO version of an existing CPAN module?
I've been avoiding naming it because I'm really interested more in high level thoughts about process, procedure, and best practices around recreating an existing CPAN module with an OO interface, as opposed to the details of the module itself.
I'd really like to hear more thoughts and recommendations on how to handle this in the general sense. Is it best to combine the procedural and OO interface into a single package? Or have them in separate packages? Why is one better? Or is there no real consensus on this, and no real advantage or disadvantage to either method?
However, for the sake of completeness, the module is Net::Statsd. It uses a pair of package variables to set the destination host/port, and I have a need to for multiple separate destinations.