From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: IDE Date: Mon, 12 Oct 2015 08:11:20 -0700 (PDT) Message-ID: <8e344c46-af2f-48c8-bbc6-64be5e4b68b2@default> References: <5610207A.2000300@harpegolden.net> <83fv1r3gzp.fsf@gnu.org> <83bncf3f9k.fsf@gnu.org> <5610E0BC.8090902@online.de> <83si5r106e.fsf@gnu.org> <831td9z18h.fsf@gnu.org> <5612E996.7090700@yandex.ru> <83bnc7tavr.fsf@gnu.org> <5618C92A.3040207@yandex.ru> <83a8rrt9ag.fsf@gnu.org> <5618D376.1080700@yandex.ru> <831td3t62e.fsf@gnu.org> <561A6199.1020901@cumego.com> <561B9D87.70504@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1444662808 18211 80.91.229.3 (12 Oct 2015 15:13:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 12 Oct 2015 15:13:28 +0000 (UTC) To: Tom , emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Oct 12 17:13:16 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Zlemo-0006PD-VL for ged-emacs-devel@m.gmane.org; Mon, 12 Oct 2015 17:13:15 +0200 Original-Received: from localhost ([::1]:56033 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zlemo-0007ZG-Lv for ged-emacs-devel@m.gmane.org; Mon, 12 Oct 2015 11:13:14 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50648) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZlelA-0005uU-7y for emacs-devel@gnu.org; Mon, 12 Oct 2015 11:11:37 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zlel6-0002ml-4a for emacs-devel@gnu.org; Mon, 12 Oct 2015 11:11:32 -0400 Original-Received: from userp1040.oracle.com ([156.151.31.81]:33537) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zlel5-0002mT-U2 for emacs-devel@gnu.org; Mon, 12 Oct 2015 11:11:28 -0400 Original-Received: from userv0022.oracle.com (userv0022.oracle.com [156.151.31.74]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t9CFBM9X017324 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 12 Oct 2015 15:11:22 GMT Original-Received: from userv0122.oracle.com (userv0122.oracle.com [156.151.31.75]) by userv0022.oracle.com (8.13.8/8.13.8) with ESMTP id t9CFBMpH001662 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 12 Oct 2015 15:11:22 GMT Original-Received: from abhmp0011.oracle.com (abhmp0011.oracle.com [141.146.116.17]) by userv0122.oracle.com (8.13.8/8.13.8) with ESMTP id t9CFBLZx010871; Mon, 12 Oct 2015 15:11:22 GMT In-Reply-To: X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6691.5000 (x86)] X-Source-IP: userv0022.oracle.com [156.151.31.74] X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.4.x-2.6.x [generic] X-Received-From: 156.151.31.81 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:191349 Archived-At: > > TAGS files are typically for definitions, but they can be for > > anything, including "usages of fields, methods, types". You > > could have different TAGS files for each of these "usages", > > and use (search) them selectively or together. >=20 > What if different objects have fields or methods of the same name? >=20 > E.g. there is field called 'name' in lots of classes and I want to > find all usage of a name field, but only with certain object types > and there is code like: >=20 > obj->name That's why I mentioned creation of TAGS files that make such distinctions. Separate files for separate such usages, for example. (The files can be mixed-and-matched when used.) A TAGS file is just an index. It can index anything you like - not just function and variable definitions. Of course, as I said, code to write such sophisticated TAGS files would need to be written. > TAGS files have considerable limitiations compared to techniques > which actually understand the code. TAGS files are written by programs that "actually understand the code". The understanding of the existing tags-file-creation programs is not up to the task. Granted. But a program that does understand the code in a deeper way could write better TAGS files. That was my point. IOW, the answer is not there yet, but TAGS files were designed for precisely this use, and they have been used for it for a long time. What's needed is code that writes the TAGS files needed today, for the languages and contexts used today.