Re: Re^3: Things every perl programmer should know? (disabled warnings)

[Juerd]

in reply to Re^3: Things every perl programmer should know? (disabled warnings)
in thread Things every perl programmer should know?

no warnings 'once'; because that sodding warning has never caught anything for me that strict wouldn't have trapped sooner. The kicker is that fixing it requires jumping through very silly hoops to make it go away.

I find that error message very useful. It's not just catching spelling errors, which strict does indeed do better, but it's also catching variables that you really did use once. Variables used once are useless.

If you have a variable that is used only once, then why use that variable? You're throwing away its value if it has one, and there's a variable declared that you don't use. "Variable used only once" actually means "Hey, you forgot to remove a line during your lastmost recent refactoring" or at least "You're throwing away valuable resources". :)

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

[Aristotle]

That would be helpful, except the warning only catches package variables, which I often very well intend to set only once (usually another module's option variables, stuff like $CGI::POST_MAX). The amount of package variables used in my code is very nearly zero anyway, and I scope my lexicals as tightly as possible (I don't reuse temporary variables either) so leftovers are a pretty much a non-issue.

In summary, all that warning has ever managed to do for me is to cause mild to immense irritation, without any benefit whatsoever.

Makeshifts last the longest.