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: Sat, 24 Oct 2015 10:00:34 -0700 (PDT) Message-ID: <4f369ede-790e-4ce9-b523-208bf1783924@default> References: <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> <87vb9wcpw9.fsf@esperi.org.uk> <83eggkwdgh.fsf@gnu.org> <87io5wcjro.fsf@esperi.org.uk> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1445706100 14347 80.91.229.3 (24 Oct 2015 17:01:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 24 Oct 2015 17:01:40 +0000 (UTC) Cc: emacs-devel@gnu.org, esperanto@cumego.com, adatgyujto@gmail.com, dgutov@yandex.ru To: Nix , Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Oct 24 19:01:27 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 1Zq2C1-0006ae-8L for ged-emacs-devel@m.gmane.org; Sat, 24 Oct 2015 19:01:21 +0200 Original-Received: from localhost ([::1]:45023 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zq2C0-00016e-P9 for ged-emacs-devel@m.gmane.org; Sat, 24 Oct 2015 13:01:20 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44404) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zq2Bi-00013x-76 for emacs-devel@gnu.org; Sat, 24 Oct 2015 13:01:03 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zq2Bg-0007ti-7H for emacs-devel@gnu.org; Sat, 24 Oct 2015 13:01:02 -0400 Original-Received: from userp1040.oracle.com ([156.151.31.81]:50417) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zq2Bc-0007s8-AA; Sat, 24 Oct 2015 13:00:56 -0400 Original-Received: from userv0021.oracle.com (userv0021.oracle.com [156.151.31.71]) by userp1040.oracle.com (Sentrion-MTA-4.3.2/Sentrion-MTA-4.3.2) with ESMTP id t9OH0Zs1005263 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Sat, 24 Oct 2015 17:00:36 GMT Original-Received: from aserv0122.oracle.com (aserv0122.oracle.com [141.146.126.236]) by userv0021.oracle.com (8.13.8/8.13.8) with ESMTP id t9OH0Z7X018380 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Sat, 24 Oct 2015 17:00:35 GMT Original-Received: from abhmp0016.oracle.com (abhmp0016.oracle.com [141.146.116.22]) by aserv0122.oracle.com (8.13.8/8.13.8) with ESMTP id t9OH0Zed006725; Sat, 24 Oct 2015 17:00:35 GMT In-Reply-To: <87io5wcjro.fsf@esperi.org.uk> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9 (901082) [OL 12.0.6691.5000 (x86)] X-Source-IP: userv0021.oracle.com [156.151.31.71] 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:192554 Archived-At: > > For references, you are supposed to use ID-Utils or something similar, > > which use a different format of their DB. >=20 > Two different tools, for more or less identical jobs except that one is > one->many and the other is many->one? (In particular, the hard part > isn't the data structure, but the parsing.) What prevents someone from creating a TAGS file that includes "references" as (additions forms of) "definitions"? How is adding references different in principle from adding, say, handling of defstructs to a program that previously only handled defuns and defvars? You can index pretty much anything. You could presumably even create a full-text index and write it out as a TAGS file, if you were up to it. (But I agree: the hard part is the parsing. The TAGS file data structure is not the problem.)