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: Tue, 04 Mar 2014 18:49:31 +0100 Message-ID: <87wqg9hn10.fsf@fencepost.gnu.org> References: <83sirj9cyp.fsf@gnu.org> <20140217203145.71a849f7@forcix.jorgenschaefer.de> <837g8t8ouc.fsf@gnu.org> <20140219080524.25689b6b@forcix.jorgenschaefer.de> <83k3cr58o2.fsf@gnu.org> <530BAEE5.9040004@online.de> <87ppmatkpe.fsf@uwakimon.sk.tsukuba.ac.jp> <87wqgfsxsr.fsf@uwakimon.sk.tsukuba.ac.jp> <87wqgf37n4.fsf@fencepost.gnu.org> <87ha7gshu9.fsf@uwakimon.sk.tsukuba.ac.jp> <871tyko9l5.fsf@fencepost.gnu.org> <87eh2ks897.fsf@uwakimon.sk.tsukuba.ac.jp> <87fvn0mk25.fsf@fencepost.gnu.org> <87bnxorlol.fsf@uwakimon.sk.tsukuba.ac.jp> <877g8bmxal.fsf@fencepost.gnu.org> <877g8asfl0.fsf@uwakimon.sk.tsukuba.ac.jp> <8738iyjrl3.fsf@fencepost.gnu.org> <87mwh5ridq.fsf@uwakimon.sk.tsukuba.ac.jp> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1393955379 22072 80.91.229.3 (4 Mar 2014 17:49:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 4 Mar 2014 17:49:39 +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 Tue Mar 04 18:49:48 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 1WKtTO-0003cC-Qe for ged-emacs-devel@m.gmane.org; Tue, 04 Mar 2014 18:49:46 +0100 Original-Received: from localhost ([::1]:47160 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKtTO-0001es-ES for ged-emacs-devel@m.gmane.org; Tue, 04 Mar 2014 12:49:46 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44667) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKtTL-0001eX-Kz for emacs-devel@gnu.org; Tue, 04 Mar 2014 12:49:44 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WKtTK-0000dl-CK for emacs-devel@gnu.org; Tue, 04 Mar 2014 12:49:43 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:44234) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKtTK-0000dh-8v for emacs-devel@gnu.org; Tue, 04 Mar 2014 12:49:42 -0500 Original-Received: from localhost ([127.0.0.1]:51409 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WKtTI-0000Qq-O9; Tue, 04 Mar 2014 12:49:41 -0500 Original-Received: by lola (Postfix, from userid 1000) id 44AD3E04EF; Tue, 4 Mar 2014 18:49:31 +0100 (CET) In-Reply-To: <87mwh5ridq.fsf@uwakimon.sk.tsukuba.ac.jp> (Stephen J. Turnbull's message of "Wed, 05 Mar 2014 02:19:45 +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:170136 Archived-At: "Stephen J. Turnbull" writes: > David Kastrup writes: > > A lot of misrepresentations. Two are important to Emacs: > > > And it is most certainly not an "attack" if Emacs developers are > > told that Emacs' C/C++ modes should not be equipped with features > > that can only work by using Clang internally, consequently > > restricting the supported languages > > This was the fifth time in your post you've made the unsupported claim > that use of Clang involves restricting the languages supported by > Emacs to those supported by Clang. Language support implemented by letting Emacs call an external parser. That's what this thread is about. If the only external parser that can be called for this purpose is Clang, the languages and dialects supported by this feature will be those implemented by Clang. > Please document people advocating that no other technology than Clang > should be used to implement "smart completion". We are not talking "should be used". We are talking "can currently be used" for functionality that has apparently already slipped into ELPA. > Surely =D3scar advocates Clang (or other AST-producing front end) as the > most accurate way to do that, but I didn't see him (or anyone else) > anywhere say that no other techniques should be allowed. If it is "the most accurate" way, how is that _not_ promoting the use of Clang for Emacs functionality. > In any case, Richard's argument nowhere depends on *exclusive* use of > Clang. He simply doesn't want unique features of Clang supported, no > matter how good Emacs's support for GCC is. Sigh. I don't know _how_ often I have to repeat this. The problem is not "supporting features of Clang", the problem is _requiring_ features of Clang for supporting features of Emacs. We don't want Emacs features that _depend_ on Clang. --=20 David Kastrup