NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
every Perl script that says:
"Don't be stupid."
--Larry Wall
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Not Too Critical (Score:2)
You're not being too critical. I expect to see such sloppy work out of CS students or new programmers, but it should never work it's way into the professional code.
Now that's what I think. The reality is, I have funny notions about software design. I think that professional software should have a test suite, preferably one that can also run on the end-users system. Many would argue that point with me. Few would argue that a test suite is a bad idea, but many might argue that it's not necessary ("I do
Re:Not Too Critical (Score:2)
Test suites are not part of the "culture" everywhere. It appears to be a language-thing. Perl (as do other languages) come with frameworks to write tests. For other languages there appears to be no such standard. I've hardly ever seen a C library coming with a test suite. And the remarkable thing is: Most often they work splendidly. Maybe it's because a good C programmer's mind is trained to expect trouble everywhere so over the time he has developed skills and techniques to write robust code.
At least there are always things he double- and triple-checks before letting them pass because they otherwise bite back so easily.
Reply to This
Parent