http://qs321.pair.com?node_id=1225971


in reply to Re^11: B::Xref buggy?
in thread B::Xref buggy?

> give the same number

"would give" the same number if Xref was ever fixed.

edit

To be clear: line numbers in Perl will never be 100% exact, because statements can span several lines, and because sometimes multiple statements are optimized into a single one.

But there is no reason (AFAIK) why a variable should be skipped from a report or the declaration being reported after the first use, like Xref is doing now.

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

Replies are listed 'Best First'.
Re^13: B::Xref buggy?
by ikegami (Patriarch) on Nov 17, 2018 at 20:13 UTC

    No, without change. When they both give a line number for an op, it matches. The reason is they get they info from exactly the same place.

      > No, without change.

      I've already proven that this is not happening now. And Dave already confirmed it.

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

        No, you showed Concise giving the line number of the while loop, and Xref giving the line number of the my. Those are different ops. Concise doesn't even try to give the line number of the my because it's not stored anywhere. Xref gets it from the nearest preceding nextstate, which is the one from the last statement of the loop.