It's true about "use", but "require" doesn't. And that could be the ticket for making modulinos less weird on the command line.
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
"This flexibility is a common feature in Python ..."
And who needs it? Here's what you cannot do in Python that you can in Perl and Ruby: run Python as an ad hoc filter. So there is that. If you are trying to say Python is better than Perl then you just failed.
You can't do that in Python! But you can run a .pm file as a script if you are dumb enough to think that's a good thing.
perl -pi.bak -e's/foo/bar/g' python.txt
I think it will work through a symlink. I.e., /bin/something -> path_to_pm