Recently while working on Text::Quote and Data::BFDump I came across this debate as well. There are unfortunately more sides to it than you post here.
For instance, I want to have certain functionality that another module has, but I dont want my module unusable if they dont have that module. What to do? Farm it out if the other is there but fallback to a local implementation? Completely use your own and remove the dependency?
Also sometimes you need features of other mdules in your module. Do you then go on to expose those features through your own interface or force the user to use two seperate objects?
I have to say that I have gone both ways, sometimes exposing the functions sometimes not. I think this is one of the areas where the "Art" of rpogramming comes in. Some people seem to know just exactly where to draw the line, others do not. Unfortunately im one of the later.
But having siad that I would say that the rule from cooking probably applies: too much seasoning can spoil the soup.
Yves / DeMerphq
---
Writing a good benchmark isnt as easy as it might look. |