I think you have it wrong on two counts:and as usual, I disagree with you entirely (grin) But thank you for feeding back, ALL feedback is appreciated.
If you can't justify the benefits of your approach towards your boss, turning to us is a bad technique.I emphasize using Perl as a community language and am turning to you to get perspectives on an interesting subject about Perl software engineering. What exactly is wrong about soliciting the advice of a respected bunch of peers on a subject?
Your argument regarding the MANIFEST is a strawman - you can easily write a Perl program to maintain your MANIFEST file.make manifest does that already, now that I recall.
why do you think you need to install just for testing? Just run your tests using perl -I lib from your distribution directory and you're all set.I dont mean testing the modules, I mean testing the (web/command-line) app which uses the modules.
In reply to Re^2: modular app development - where do your modules live?
by metaperl
in thread modular app development - where do your modules live?
by metaperl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |