Re^2: Portably unit testing scripts (no modulinos)

What purpose does that modulino stuff serve anyway?

The idea is to make unit testing of applications easier/possible, since the main control flow gets put into a subroutine that can be unit tested like any other sub.

The most it can accomplish is to to substitute 1 symlink for 1 regular file -- thats silly golf , esp in a distribution

What? It's not designed to shorten (golf) anything... in fact, the code is a bit more verbose. And it has nothing to do with the filesystem.

pod2usage exitval does accept "noexit"

That's right, "NOEXIT" would help with testing the --help / pod2usage() path. Unfortunately that doesn't help the general case, though.

Comment on Re^2: Portably unit testing scripts (no modulinos) Download Code

Replies are listed 'Best First'.
Re^3: Portably unit testing scripts (no modulinos) by Anonymous Monk on Oct 26, 2019 at 09:32 UTC
Having a main sub and all code in subs is plain modularity. The modulino part is unless caller. Deciding if act as a module or program based on caller is silly modulino golf.	[reply]