in reply to To USE or not to USE
My feelings are such that if we intend to only use less than 50% of what the module offers we are better writing the function our selves.
In this case, quantity doesn't matter.
Let's say you need to use a database. The DBI has a few dozen methods, but you just need to use connect, selectall_arrayref, and disconnect.
Would you write those methods yourself or would you use DBI?
Think about what's behind those three methods, in terms of complexity, efficiency, and testing. I'm sure you don't want to go through such ordeal.
That's just an example, but I could say the same for a dozen modules that I use on a daily basis.
IMO, you should use what is well tested and established, and rewrite only if you have a really strong reason for that, such as buggy code and unresponsive author.
_ _ _ _ (_|| | |(_|>< _|
|
|---|
| Replies are listed 'Best First'. | |
|---|---|
|
Re: Re: To USE or not to USE
by MidLifeXis (Monsignor) on Jul 23, 2003 at 16:58 UTC |