From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Emacs contributions, C and Lisp Date: Wed, 26 Feb 2014 07:53:35 +0100 Message-ID: <87eh2q74b4.fsf@fencepost.gnu.org> References: <831tz5daes.fsf@gnu.org> <8738jlohd6.fsf@yandex.ru> <83txc1bl83.fsf@gnu.org> <5300189A.9090208@yandex.ru> <83wqgv9fbj.fsf@gnu.org> <20140216180712.236069f6@forcix.jorgenschaefer.de> <87wqgr4v18.fsf@yandex.ru> <53064BD0.7070009@yandex.ru> <87ha7tr5bo.fsf@fencepost.gnu.org> <87ppmhecd8.fsf@yandex.ru> <87y50z90pd.fsf@fencepost.gnu.org> <87txbn8r6x.fsf@fencepost.gnu.org> <87r46qtn8b.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1393397642 9741 80.91.229.3 (26 Feb 2014 06:54:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 26 Feb 2014 06:54:02 +0000 (UTC) Cc: emacs-devel@gnu.org To: "Stephen J. Turnbull" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 26 07:54:11 2014 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 1WIYNd-0004yW-CB for ged-emacs-devel@m.gmane.org; Wed, 26 Feb 2014 07:54:09 +0100 Original-Received: from localhost ([::1]:38478 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIYNd-0005MG-1U for ged-emacs-devel@m.gmane.org; Wed, 26 Feb 2014 01:54:09 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46971) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIYNY-0005KB-VD for emacs-devel@gnu.org; Wed, 26 Feb 2014 01:54:05 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WIYNX-0002qc-R6 for emacs-devel@gnu.org; Wed, 26 Feb 2014 01:54:04 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:35721) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIYNX-0002qS-O2 for emacs-devel@gnu.org; Wed, 26 Feb 2014 01:54:03 -0500 Original-Received: from localhost ([127.0.0.1]:42893 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WIYNW-0001yl-Oe; Wed, 26 Feb 2014 01:54:03 -0500 Original-Received: by lola (Postfix, from userid 1000) id EC913E0478; Wed, 26 Feb 2014 07:53:35 +0100 (CET) In-Reply-To: <87r46qtn8b.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Wed, 26 Feb 2014 15:13:56 +0900") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2001:4830:134:3::e 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:169879 Archived-At: "Stephen J. Turnbull" writes: > David Kastrup writes: > > > In this particular case, the "annotated syntax tree" question in > > particular is mostly uninteresting since we are talking about > > characterizing identifiers. It is "mostly" uninteresting since the > > resolution of an identifier depends on scopes, > > Nice try, but I don't think you can deprecate the value of the > information GCC is not allowed to emit that easily. > > Emacs's treatment should depend on types and usage [...] Most of your reply has already been addressed in the parts you did not quote. If the discussion is supposed to lead somewhere rather than run in circles, it would make sense not to cherry-pick one's controversy. At the current point of time, you are trying to retract the discussion back into discussing general principles. We had hit a wall with that approach already, so unless we particularly like that wall, I suggest that we go back to the specific problem of completion, figure out the respective approaches leading to solutions there, and try figuring out lessons for other applications afterwards. -- David Kastrup