Re^2: warnings under the debugger

Therefore I am still suggesting that an explanation for the symptoms is that, to use Anno's words, the debugger "starts a new interpreter each time ..." ... it reads the keyboard input and uses "string eval" on it instead of submitting it directly to Perl.

-M

Free your mind

Comment on Re^2: warnings under the debugger

Replies are listed 'Best First'.
Re^3: warnings under the debugger by Anno (Deacon) on Mar 08, 2007 at 21:14 UTC
When I tried it (I don't use the debugger normally), I found that the warning is shown, if warnings are switched on. Here is a (slightly edited) session: `anno@oliva> perl -wd -e '' Loading DB routines from perl5db.pl version 1.28 [...] DB<1> $x = { 1 } Odd number of elements in anonymous hash at (eval 10)[/usr/local/lib/p +erl5/5.8.7/perl5db.pl:628] line 2. [...]` [download] So it seems the debugger has ways of restoring the warning state of the outer interpreter in an `eval`. (Can't be that hard). Why the original poster didn't see the warning remains an open question. Anno	[reply] [d/l] [select]
Re^4: warnings under the debugger by Moron (Curate) on Mar 12, 2007 at 14:14 UTC
Yes, I see your point. I think it's because -w (which you used in your test) makes the debugger eval with warnings as well whereas -Mwarnings (which the OP used instead) loads the warnings pragma as if it were explicitly loaded for the code being debugged while leaving the debugger's own separate interpreter instance unaffected. -M Free your mind	[reply]