Re^2: Problem of scope : $SIG{__WARN_

Sure I tried it. unfortunately It doesn't work; either I put

$SIG{__WARN__} = sub { set_dberror(join('',@_))};
[download]

at the beginning of the module and it changes behaviour of all programs using it; I tried too

local $SIG{__WARN__} = sub { set_dberror(join('',@_))};
[download]

at the beginning of the module, but it just has no effect at all (the dbi errors are happily sput out on STDERR).

Comment on Re^2: Problem of scope : $SIG{__WARN__} in a module... Select or Download Code

Replies are listed 'Best First'.
Re^3: Problem of scope : $SIG{__WARN__} in a module... by radiantmatrix (Parson) on Dec 03, 2004 at 20:59 UTC
Firstly, you can get DBI to stop spitting errors by: `$dbh->{PrintError} = 0;` [download] Secondly, `$SIG{__WARN__}` doesn't automagically cover anything printed to STDERR, only things that result from a call to `warn()`, which happens to cause a print to STDERR. Finally, if neither of those applies, try: `our $SIG{__WARN__} = sub { ... }` [download] For which I'm certain I will be flamed... radiantmatrix `require General::Disclaimer; s//2fde04abe76c036c9074586c1/; while(m/(.)/g){print substr(' ,JPacehklnorstu',hex($1),1)}`	[reply] [d/l] [select]
Re^4: Problem of scope : $SIG{__WARN__} in a module... by wazoox (Prior) on Dec 04, 2004 at 13:07 UTC
Ach, using `our` didn't come to my mind. I'll give it a try just in case... PS Why would you be flamed?	[reply] [d/l]