|There's more than one way to do things|
Following up: Re: LWP oddityby adamsj (Hermit)
|on Nov 13, 2002 at 18:12 UTC||Need Help??|
I hadn't thought to set LWP::Debug (and did you know that Perl and LWP doesn't deal with LWP::Debug at all?), but now I have, and am getting much the same result when the proxy statement is removed. Without proxy, the output from LWP::Debug is:
and here the debugger dies, along with the script.
With the proxy statement left in, I get:
and the debugger stays alive and ready to proceed.
On the off-chance this was an artifact of the debugger, I ran without the -d flag and sprinkled in some print statements. This didn't produce any change--LWP::Debug gave the same output and I died in the same place.
So at this point, I'm slightly stumped. I suppose my next move is either to give up and say "What the heck do I care? It works, doesn't it?" or step laboriously through the LWP code itself to see where it dies.
I'm certainly open to a better idea than either of those two.
Afterthought: I'm running 5.6.1. LWP is version 5.63.
They laughed at Joan of Arc, but she went right ahead and built it. --Gracie Allen