Re: Debugger line numbering anomaly

[BillKSmith]

At one time, I had this problem with code that did not conform to all the specifications in perlstyle. In this case:

•Long lines broken after an operator (except and and or).

I do not know if this issue has been fixed because I now routinely use perltidy. Even if this does not fix your issue, it is a good practice. The book "Perl Best Practices" recommends "break before operator". I have never had a problem with this exception.

[LanX]

The debugger doesn't parse the code, it simply assigns every line found to an internal array, according to line-endings "\n" and shows them in accordance to the compiled line-numbers.

Now if the Perl compiler got confused by multi-lines (very unlikely), this could be demonstrated by including a warn message.