Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

Re: When should you not use strict and warnings?

by CountZero (Bishop)
on Dec 27, 2012 at 16:04 UTC ( #1010544=note: print w/replies, xml ) Need Help??

in reply to When should you not use strict and warnings?

I never switch off use strict but I used to disable use warnings for production code (but only after it ran clean of course).

Nowadays I always use Modern::Perl with enables both strict and warnings and I do not bother with disabling it anymore in production code. In rare cases I might locally disable irrelevant but well understood warnings for unititalized variables.

I use Perl mainly for transforming data from one format to another and when an unexpected "unitialized variable" warning crops up, it ususally means that there is something wrong with the data and the parser I wrote has failed to match some data to a variable, hence the warning. I think this warning is a nice last resort catch-all line of defence and I would not want to miss it.


A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James

My blog: Imperial Deltronics

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1010544]
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (7)
As of 2018-06-25 10:35 GMT
Find Nodes?
    Voting Booth?
    Should cpanminus be part of the standard Perl release?

    Results (126 votes). Check out past polls.