Re: "set-check" warning
Michael Yount <[email protected]>
| Newsgroups | gmane.mail.majordomo.majordomo2.devel |
|---|---|
| Message-ID | <[email protected]> |
On 13 Jan 14:28, Brock Rozen wrote: > >The "next" statement on line 1047 will go to the next iteration of the > >loop, so the debugging statement should be used on the previous line > >instead. > > --== The flag value is [email protected] at blib/lib/Mj/List.pm > (autosplit into blib/lib/auto/Mj/List/get_setting_data.al) line 1047. > --== Use of uninitialized value in string eq at blib/lib/Mj/List.pm > (autosplit into blib/lib/auto/Mj/List/get_setting_data.al) line 1048. So, the e-mail address has been added to the list of possible delivery classes somehow. Does the following patch solve the problem without causing any side effects? Michael --- lib/Mj/List.pm 11 Nov 2005 20:50:12 -0000 1.158 +++ lib/Mj/List.pm 13 Jan 2006 19:18:16 -0000 @@ -462,7 +462,7 @@ $rset = $flags{$inv}->[0]; $isflag = $inv; } - elsif ($rset = $classes{$class[0]}->[0]) { + elsif (exists $classes{$class[0]} and $rset = $classes{$class[0]}->[0]) { $isflag = 0; } else {