Re^6: Developing code to be a module (perl -lanse)

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 :)

Comment on Re^6: Developing code to be a module (perl -lanse)

Replies are listed 'Best First'.
Re^7: Developing code to be a module (perl -lanse) by space_monk (Chaplain) on May 01, 2013 at 16:51 UTC
The item of code you have quoted is what is known as an example; if it were used in a professional environment you would write a unit test for it. Unit tests have a purpose; if someone comes along to improve the code, then they can verify that their changes do not screw it up in any way. If you spot any bugs in my solutions, it's because I've deliberately left them in as an exercise for the reader! :-)	[reply]
Re^8: Developing code to be a module (professionalism) by Anonymous Monk on May 02, 2013 at 04:06 UTC
The item of code you have quoted is what is known as an example; Sure its not; yeah, its in the example directory, but it does a real job , and does it well, and comes with documentation; it is a real useful program if it were used in a professional environment you would write a unit test for it... Maybe it is being used in "a real professional environment"? Maybe different environments have different standards? Maybe, there is a threshold, for when to turn stuff into modules, when to write unit tests?	[reply]