in reply to
module w/ object-oriented and functional interfaces: best practices?
Echoing BrowserUK’s comments, and after up-voting his post, I would emphasize that a running, stable application is a very important thing not to be changed lightly. In my experience it is best to add objects to existing applications, when and where and if that makes sense, and to generally let a sleeping dog lie.
Perl’s implementation of objects is just as pragmatic as the rest of the language. A constructor routine, with a by-convention choice of name, that returns a blessed (hash...) reference; a fast-and-efficient notion of “blessed,” and the blessed-reference is always the implied first parameter to the function. This gets the job done simply and efficiently without compelling you to seriously change either your thinking or your code. (Typical battle-tested Perl wisdom ...)
Yes, the object paradigm (in Perl) is quite useful, because it gives you “a convenient briefcase in which to store your coat,” or anything and everything else that you need to carry around with you, and it makes sure that you won’t misplace it. Plus, a naturally-simplified calling convention for the clients to use. Yes, lots of formerly-function based packages did “convert” to an object API, but then again, I daresay that there are other packages that went the other way. They didn’t do it because someone just felt embarrassed about how the package worked before.
“Best Practice” is, and forever will be, a general guideline ... a frequently-beneficial categorical suggestion, but made by someone who does not know and cannot know your application’s unique situation. But I would not tamper with what works, just because of it. Rather, I would permit my application to evolve naturally, trending in this new direction as it makes logical business-sense to do so.