Re^2: Why does an undef argument in a join produce this warning?

Replies are listed 'Best First'.
Re^3: Why does an undef argument in a join produce this warning? by mscharrer (Hermit) on Apr 24, 2008 at 08:37 UTC
You already have the solution for this case. If you ever have issues with unwanted warnings again, you should know that there can be specifically deactivated locally in the current scope. E.g. if you know that one function can cause this warning and the only way around would be massive use of `if defined` you can just say `no warnings 'uninitialized';` to tell Perl that you don't want this specific warning inside the current scope, i.e. sub function or `{ }` block, etc.	[reply] [d/l] [select]
Re^4: Why does an undef argument in a join produce this warning? by wade (Pilgrim) on Apr 24, 2008 at 16:04 UTC
Of course, in this case, the warning pointed to a bug... -- Wade	[reply]