BTW, you shouldn't treat using strict and warnings as beneficial, you should treat it as mandatory. There are so many "stupid programmer" mistakes I've made, time and time again - typos and scoping issues for starters - that I really don't want to write any more code that doesn't urn on strict and warnings.

Not to belabor the point, but the topic is often brought up here. In fact, the "weekly best" post is currently Warnings and Strict in Production/Performance, where you see a lot of the monks around here encouraging use of strict and warnings.

You can also use diagnostics; along with warnings, which will print a "layman's summary" of the warnings your script causes. (This one should be turned off for production use, IMHO). Being confused at the extra messages is normal at first, and you can always bring questions up to the fine folk here at the monastery. Once you're able to decipher them easily enough on your own, you'll wonder how you ever lived without these valuable development tools.

Update: McDarren is right, which is why I did belabor it a bit ;) There is so much good reading, questions solved by, meditations, etc. here on the monastery.

s**lil*;  $*=join'',sort split q**;  s;.*;grr; &&s+(.(.)).+$2$1+; $; =
qq-$_-;s,.*,ahc,;$,.=chop for split q,,,reverse;print for($,,$;,$*,$/)
[download]