Re^10: B::Xref buggy?

> Concise and Xref will give the same line number in that scenario.

Not at the moment. As it turned out Xref is buggy.

see here again.

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery
FootballPerl is like chess, only without the dice}

Comment on Re^10: B::Xref buggy?

Replies are listed 'Best First'.
Re^11: B::Xref buggy? by ikegami (Patriarch) on Nov 17, 2018 at 20:09 UTC
Yes, at the moment. I don't know why you link to that post because Concise doesn't give a number for the `my`, and Xref doesn't give a line number for the `while`.	[reply] [d/l] [select]
Re^12: B::Xref buggy? by LanX (Saint) on Nov 17, 2018 at 20:12 UTC
> 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}	[reply]
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.	[reply]
Re^14: B::Xref buggy? by LanX (Saint) on Nov 17, 2018 at 20:18 UTC
Re^15: B::Xref buggy? by ikegami (Patriarch) on Nov 17, 2018 at 20:21 UTC
Some notes below your chosen depth have not been shown here


Do you know where your variables are?
	PerlMonks