|
From: | Dmitry Gutov |
Subject: | bug#20629: 25.0.50; Regression: TAGS broken, can't find anything in C++ files. |
Date: | Sat, 30 May 2015 01:36:56 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0 |
On 05/29/2015 11:35 PM, Eli Zaretskii wrote:
xref expects more accurate results, because it shows them all at once, instead of one by one, in some order that assures the users will only ever see the few first ones. So yes, I'd say the switch to xref puts a different kind of pressure on what etags/ctags does.
It does exert some pressure, but mostly to ensure that when a user searches for a "symbol" that they see in a buffer, it should have an explicit or an implicit tag match.
Whether qualified tag names are included in the completion, and whether one can search for a qualified tag name reliably, that hasn't changed between find-tag and xref-find-definitions.
foo::bar::baz is standard C++, AFAIK, so the ambiguity is already known to C++ programmers.
I'm not disputing that.
[Prev in Thread] | Current Thread | [Next in Thread] |