Re^3: Understanding how to *use* a CPAN module

I see you got it "working", but here's a thought. Why does that suite of modules have all those setter methods when the isbndb api is read-only?

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority".

In the absence of evidence, opinion is indistinguishable from prejudice.

Comment on Re^3: Understanding how to use a CPAN module

Replies are listed 'Best First'.
Re^4: Understanding how to use a CPAN module by bradcathey (Prior) on Apr 22, 2008 at 16:50 UTC
Ha! No clue. I actually did ask myself that, but obviously I'm no expert on this module :-) —Brad "The important work of moving the world forward does not wait to be done by perfect men." George Eliot	[reply]
Re^5: Understanding how to use a CPAN module by BrowserUk (Patriarch) on Apr 22, 2008 at 18:00 UTC
but obviously I'm no expert on this module :-) Me neither, but I'd hazard a guess that the justifiction would be "completeness". Which could be paraphrased as: complication for the sake of dogma. This is a prime example of the latter of the two greatest evils in software development today: What-if pessimism and Wouldn't-it-be-nice-if optimism.. Writing extra code now, "in case it might become useful later" costs both up-front and in ongoing maintenance. Not to mention the dibilitating affect it has on the clarity of the documentation. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". In the absence of evidence, opinion is indistinguishable from prejudice. "Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."	[reply]