Re: How would you use perl debugging tools to pinpoint the problem here?

I ran into this problem "in the wild" and asked about it here. The really bad part is that you can't even catch it with perl -c.

Comment on Re: How would you use perl debugging tools to pinpoint the problem here? Download Code

Replies are listed 'Best First'.
Re^2: How would you use perl debugging tools to pinpoint the problem here? by blazar (Canon) on Nov 10, 2005 at 16:42 UTC
Personally I don't say any reason why it should be caught with `perl -c`. It's not a syntax error after all. To be precise it's not an error at all. Depending on the hardware, the OS and the OS configuration, it may run just smooth...	[reply] [d/l]
Re^3: How would you use perl debugging tools to pinpoint the problem here? by VSarkiss (Monsignor) on Nov 10, 2005 at 17:26 UTC
No, it's not an error, but it's a construct that, because of the well-meaning but misguided "optimization", causes the compiler to freeze up, and the OP was asking for ways that Perl itself, such as in the debugger, could help you figure out what was going on. Usually, `perl -c` is one of those ways, but not in this case. Brother tye's reply in that thread is an excellent illustration of what I think the problem is. Do not rebuke them with harsh words ... but rather lead them gently - with URLs - so that they may learn wisdom.	[reply] [d/l]