very few professional software development environments would be based on the CPAN packaging system (it could probably be done, but would seem like a kludge
I'm curious why you think the CPAN packaging system would seem like a kludge. I've always used EU:MM (or more recently Module::Build) for my commercial work with great success. Why would I bother reinventing the wheel?
The ways people really do it would be interesting to hear about (just as an example: is there any standard at all outside of the h2xs world about where to put test files and what to name them?
I often find myself with a hierarchy of test classes that I put in t/lib that mirrors the files in lib/.
In reply to Re^4: Unwritten Perl Books
by adrianh
in thread Unwritten Perl Books
by Ovid
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |