Lines Matching defs:FATAL

361         if ($word eq 'FATAL') {
393     # "FATAL" or "NONFATAL")
395         if !@_ || (@_==1 && ($_[0] eq 'FATAL' || $_[0] eq 'NONFATAL'));
399         if($warning =~ /^(NON)?FATAL$/) {
417     # append 'all' when implied (empty import list or after a lone "FATAL")
418     push @_, 'all' if !@_ || @_==1 && $_[0] eq 'FATAL';
423         if ($word eq 'FATAL') {
440 sub FATAL () { 2 };
514     foreach my $type (FATAL, NORMAL) {
524     return if ($wanted & (NORMAL | FATAL | MESSAGE))
525                       == (NORMAL | FATAL | MESSAGE)
585     return __chk(FATAL, @_);
590     return __chk(FATAL | MESSAGE, @_);
595     return __chk(NORMAL | FATAL | MESSAGE, @_);
605     return __chk(FATAL | LEVEL, @_);
610     return __chk(FATAL | MESSAGE | LEVEL, @_);
615     return __chk(NORMAL | FATAL | MESSAGE | LEVEL, @_);
620 delete @warnings::{qw(NORMAL FATAL MESSAGE LEVEL)};
1107 The presence of the word "FATAL" in the category list will escalate
1110 B<NOTE:> FATAL warnings should be used with care, particularly
1111 C<< FATAL => 'all' >>.
1124 defensive programming technique, using C<< FATAL => 'all' >> to fatalize
1126 risky.  Therefore, the use of C<< FATAL => 'all' >> is
1133 B<NOTE:> Users of FATAL warnings, especially those using
1134 C<< FATAL => 'all' >>, should be fully aware that they are risking future
1140 using FATAL warnings break due to the introduction of a new warning we will
1141 NOT consider it an incompatible change.  Users of FATAL warnings should
1147 and spirit.  Use of such features in combination with FATAL warnings is
1150 The following documentation describes how to use FATAL warnings but the
1164         use warnings FATAL => qw(void);
1181 To explicitly turn off a "FATAL" warning you just disable the warning
1186     no warnings FATAL => qw(void);
1193     use warnings FATAL => 'all', NONFATAL => 'syntax';
1195 As of Perl 5.20, instead of C<< use warnings FATAL => 'all'; >> you can
1199    use warnings 'FATAL';  # short form of "use warnings FATAL => 'all';"
1202 using C<< use warnings FATAL => 'all'; >>.
1205 5.20, you must use C<< use warnings FATAL => 'all'; >> instead.  (In
1207 C<< use warnings 'FATAL'; >>, C<< use warnings 'NONFATAL'; >> and
1208 C<< no warnings 'FATAL'; >> was unspecified; they did not behave as if
1292     use warnings FATAL => 'MyMod::Abc';
1421 package has been set to FATAL in the calling module.
1426 Return TRUE if the warnings category C<$category> has been set to FATAL in
1435 Return TRUE if that warnings category has been set to FATAL in the first
1450 If that warnings category has been set to "FATAL" in the calling module
1457 If the warnings category, C<$category>, has been set to "FATAL" in the
1467 If that warnings category has been set to "FATAL" in the scope where C<$object>