Skip to content

Commit

Permalink
Fix stupid test in 9uninit
Browse files Browse the repository at this point in the history
I was wondering why the warnings were being triggered backwards.
Different output handles.  Duh.
  • Loading branch information
Father Chrysostomos committed Jun 23, 2016
1 parent 1b3df0e commit d3ac935
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions t/lib/warnings/9uninit
Expand Up @@ -2167,7 +2167,7 @@ use warnings 'uninitialized';
# aelem + const
use constant foo => \0;
$SIG{__WARN__} = sub {
print
print STDERR
$_[0] =~ /\$a\[([^]]+)]/ && $1 == foo
? "ok\n"
: ("$1 != ",0+foo,"\n")
Expand All @@ -2178,5 +2178,5 @@ undef $SIG{__WARN__};
# Multideref
() = "$a[140688675223280]";
EXPECT
Use of uninitialized value $a[140688675223280] in string at - line 15.
ok
Use of uninitialized value $a[140688675223280] in string at - line 15.

0 comments on commit d3ac935

Please sign in to comment.