Whilst the example you linked to doesn't use Test:: anything, your argument is somewhat deflated by the fact that that Text::CSV_XS has extensive unit tests attached to it, according to the Manifest you linked to. :-).
Sure its not :) None of those unit-tests cover/check csv2xls, a human does that
I haven't time to examine the example you referred to in detail, so I could be wrong, but I suspect there is a case to be made for contents of the main loop to be also made into a function.
Sure there is, if you want to make it into a module, like the OP describes.
But as a stand alone program, its perfectly serviceable without being a function -- and has been since Text-CSV_XS-0.26 in 2007
Personally I'm deeply uncomfortable if someone has waffled on for 1000 lines of programming without breaking it up somehow!
I learned about it from those pythong folks, they call it whitespace, I hear it can work for anyone :)
:D
In reply to Re^6: Developing code to be a module (perl -lanse)
by Anonymous Monk
in thread Developing code to be a module
by rpnoble419
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |