in reply to Debugger line numbering anomaly

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.

Bill

Replies are listed 'Best First'.
Re^2: Debugger line numbering anomaly
by LanX (Saint) on Dec 24, 2019 at 18:09 UTC
    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.

    Cheers Rolf
    (addicted to the Perl Programming Language :)
    Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

[reply]
[d/l]

In Section Seekers of Perl Wisdom