Many programmers have subdirectories full of little test snippets; it's common to write a few programs to explore a feature of the language or a new library. It's also common to do this with false laziness, eyeballing output and tweaking an idea here or there.
Usually that's okay, but occasionally you know you wrote code to explore something you need to know right nowif only you could find it and decipher what you were thinking.
If you know how to write test cases with Perl's standard testing tools, you can end this madness and make even your experiments reusable and maintainable.read more.
Usually that's okay, but occasionally you know you wrote code to explore something you need to know right nowif only you could find it and decipher what you were thinking.
If you know how to write test cases with Perl's standard testing tools, you can end this madness and make even your experiments reusable and maintainable.read more.
Comments