comment on

Thanks, personally I rarely use the debugger for debugging, at least not with code I wrote.

To see warnings with perl -d you could try using it from an IDE like emacs to separate output frame from debugging GUI.

First I have to say that I don't have the problem that warnings aren't shown in my debugger-instance, but I tweaked a lot in the past. Anyway ...

> I comment out the line when not running in the debugger because it generates a warning message.

... you could put that code into debugger's rc-file '.perldb' or into PERL5DB environment variable to make it the default behavior of the debugger.

Like that you don't need to change the scripts. =)

this works for me

lanx@nc10-ubuntu:$ cat .perldb
sub afterinit {
  $SIG{"__WARN__"}= sub { print "$_[0]"; $DB::single=1 };
}
[download]

see perldebug for details

Cheers Rolf

( addicted to the Perl Programming Language)

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.