# The following was supposedly scribed by # Austin Schutz # on Tuesday 01 March 2005 02:13 pm:
>Often this is caused by a module author not expecting an empty list of >arguments, or similar. The author doesn't document a piece of code as > capable of throwing an exception, because they don't think it is. And of course you didn't write a test for that because you thought nobody would be stupid enough to call the function with a bunch of (or not enough) garbage. Maybe that's an argument for a Test::Garbage module or a randomly generated "t/Stupid.t". So, something else falls out of today's entropy (and I thought I was just wasting time.) While you're meditating: http://perl.overmeer.net/ "Programming is a Dark Art, and it will always be. The programmer is fighting against the two most destructive forces in the universe: entropy and human stupidity. They're not things you can always overcome with a "methodology" or on a schedule." -- Damian Conway, author of Object Oriented Perl. --Eric -- "Cleanliness is next to impossible." -- Unknown --------------------------------------------- http://scratchcomputing.com ---------------------------------------------