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: New maintainer Date: Tue, 06 Oct 2015 09:34:17 +0200 Message-ID: <87a8rwa1s6.fsf@fencepost.gnu.org> References: <874miapdhs.fsf@openmailbox.org> <8737xuuw2y.fsf@rabkins.net> <87lhbmkrle.fsf@fencepost.gnu.org> <87si5r22qh.fsf@fencepost.gnu.org> <5612CEA6.3010809@yandex.ru> <87egh95cze.fsf@gmail.com> <5612D36B.1030906@yandex.ru> <87a8rx5awg.fsf@gmail.com> <87egh9qb8t.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1444116879 14285 80.91.229.3 (6 Oct 2015 07:34:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 6 Oct 2015 07:34:39 +0000 (UTC) Cc: emacs-devel@gnu.org To: Jay Belanger Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 06 09:34:38 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 1ZjMlg-00063L-Ab for ged-emacs-devel@m.gmane.org; Tue, 06 Oct 2015 09:34:36 +0200 Original-Received: from localhost ([::1]:49362 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjMlf-0006QR-MQ for ged-emacs-devel@m.gmane.org; Tue, 06 Oct 2015 03:34:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45828) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjMlQ-0006QJ-SA for emacs-devel@gnu.org; Tue, 06 Oct 2015 03:34:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZjMlP-00025O-WE for emacs-devel@gnu.org; Tue, 06 Oct 2015 03:34:20 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:34326) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjMlO-00024U-RE; Tue, 06 Oct 2015 03:34:18 -0400 Original-Received: from localhost ([127.0.0.1]:48145 helo=lola) by fencepost.gnu.org with esmtp (Exim 4.82) (envelope-from ) id 1ZjMlO-0008HU-8H; Tue, 06 Oct 2015 03:34:18 -0400 Original-Received: by lola (Postfix, from userid 1000) id 9803ADF4A3; Tue, 6 Oct 2015 09:34:17 +0200 (CEST) In-Reply-To: <87egh9qb8t.fsf@gmail.com> (Jay Belanger's message of "Mon, 05 Oct 2015 16:03:14 -0500") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.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:191003 Archived-At: Jay Belanger writes: > "John Wiegley" writes: > >> If, on the other hand, Clang offered some clever API that was specific >> to Clang, and we built support for that API directly into Emacs to >> allow a better experience for Clang users, this is what Richard would >> not allow, according to what I read. > > Ah. This sounds different than what you wrote before: > >>> The main thing is that it is GCC's responsibility to be better, and >>> not Emacs' to prevent better options from being chosen, simply to >>> accommodate a lack of progress by GCC. > > I took this to mean if Clang offered something that Emacs could > support, then it would be GCC's responsibility to add it. If consistent with the technical possibilities and steering decisions. Yes. But it is Emacs' responsibility to wait until GCC does that before supporting it on other platforms. -- David Kastrup