in reply to Re: Modules as executable scripts?in thread Modules as executable scripts?
use requires that the module's files have a ".pm" extension.
True, but then it's "weird" to use from a program or other module:
instead of the usual:
I think it's better to put up with the weirdness in the modulino than forcing weirdness into programs and other modules that try to use the modulino.
It's true about "use", but "require" doesn't. And that could be the ticket for making modulinos less weird on the command line
modulinos are golf, which is a game, a gimmick, and not a feature to be used for work,
so say no modulinos , an evil gimmick )
If a user can be bothered to create a symlink. I.e., /bin/something -> path_to_pm
Then the user can be bothered to create
TheModule::BinSomething( @ARGV );
Its literally no effort at all to accomplish, esp if bin/something is created by the module installation software
The only thing modulinos can accomplish is to substitute 1 symlink for 1 regular file -- what a ridiculous goal to write extra code for
www.com | www.net | www.org
Hope and Pray
Hash & Salt using Acme::XKCD::DebianRandom
Hash & Salt using other rng algorithms
Printouts secured with physical locks
One of a million Post-Its sticking on the monitor
A piece of paper taped to the backside of the keyboard
Results (70 votes). Check out past polls.