strict.pm has run-time as well as compile-time checks. For example, symbolic references can only be detected at run time.

I consider dereferencing a symbolic reference to be an indication of a pretty serious error (if you wrote and tested the code under 'use strict') that I'd want that flagged in production. I fully support turning off warnings in production (though I even more support keeping warnings turned on and providing a system for the warnings to get routed to the developers so they can be "fixed").

FWI, I can't think of any warnings that are controlled by strict.pm, but that doesn't mean there aren't any. (:

        - tye (but my friends call me "Tye")