I often give the "use strictures" advice because it gives the greatest bang for the buck in terms of catching the sorts of mistakes newbie (and other) programmers make. In that respect it is cheap advice of great value.
In the case of the reply to the OP I strengthened my usual "should" to "absolutely must" because strictures would have caught several different types of error in the OP's code. A cursory test of the original code would seem to show it worked. However due to bare word errors and various other types of error Perl glosses over by default the code was not doing anything like what the OP expected.
I'm not sure why you are fixated on "cheap upvotes". If that were the only advice I ever gave maybe there would be some basis for the implied accusation, but without much work you could find out for yourself that that doesn't apply to me, or indeed to any other monk I can think of.
I sure as an experienced and competent programmer you have no need for help from the dumb computer, but for me tools such as strictures, a good IDE and unit tests make me an order of magnitude more productive with much greater confidence in my work. I shall continue to advise newbies (and anyone else who will listen) to use stictures and any other such tool that make their life easier and improves the quality of their code.
True laziness is hard work
|