david2008 has asked for the wisdom of the Perl Monks concerning the following question:

Hi all,

I want perl in the development phase to be stricter and die on use of uninitialized variables.
I did not find something with googling.
Is there a possibility to make this ?

Thanks,
David
  • Comment on cause perl to die on use of unintialized variables

Replies are listed 'Best First'.
Re: cause perl to die on use of unintialized variables
by moritz (Cardinal) on Jun 23, 2010 at 11:22 UTC 
    use warnings FATAL => qw(uninitialized);

    [download]

    should do what you want.

    Update: if you don't want to add that to your file, but rather want it confined to development uses only, you can also run your perl script as 

    $ perl -Mwarnings=FATAL,uninitialized  filename.pl

    [download]

    to get that effect without modifying your script. But beware, it can be overridden inside the script, or in modules used by the script.

    For more information on the warnings pragma, please consult perllexwarn.

    Perl 6 - links to (nearly) everything that is Perl 6.
[reply]
[d/l]
[select]
Re: cause perl to die on use of unintialized variables
by chromatic (Archbishop) on Jun 23, 2010 at 11:26 UTC

    The warnings pragma has a FATAL option:

    use warnings FATAL => 'uninitialized';

    This has a lexical scope, so you have to enable it in every scope in which you want it to take effect. See perllexwarn. Alternately you can set up your own global warn handler by sticking a code ref in $SIG{__WARN__}, but that's uglier.

[reply]
[d/l]
[select]

Back to Seekers of Perl Wisdom