I am experimenting with ASPN PDK, which comes with a (rather cool, as even a non IDE person like me has to admit) graphical debugger.
However I am also deeply addicted to the 'perl -e 42 -d' thingy to get a perl shell...
And I found out that that does not work any more! Any perl -d attempt fires up the graphical debugger. To my utter surprise, this also happens with an unrelated native 5.8 build on the same Win32 box.
After some digging in the docs, it turns out that setting a couple of environment variables (PERLDBOPTS and PERL%DB), with PERL5DB set to
resets my beloveed CLI behavior.BEGIN { require 'perl5db.pl';}
But...
How does it do it? Meaning, how can the perldebug influence a perl interpreter it knows nothing about and which should not know about perldebugger?
Just curious. I tried to delve in the perl5db.pl and perldoc perldebug, but I could not spot the magic.
Cheers,
alf
In reply to ASPN perldebug magic? by alien_life_form
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |