From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: The current state of the comment-cache branch Date: Wed, 28 Dec 2016 19:09:46 +0200 Message-ID: <83pokcugit.fsf@gnu.org> References: <20161223215056.GA2771@acm.fritz.box> <83fuldzre1.fsf@gnu.org> <20161224083054.GA2212@acm.fritz.box> <83bmw1zoy8.fsf@gnu.org> <20161224094246.GD2212@acm.fritz.box> <20161224113620.GF2212@acm.fritz.box> <20161227175500.GD2324@acm.fritz.box> <83y3z0ukth.fsf@gnu.org> <871swsf1es.fsf@thinkpad.rath.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1482945018 18276 195.159.176.226 (28 Dec 2016 17:10:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 28 Dec 2016 17:10:18 +0000 (UTC) Cc: emacs-devel@gnu.org To: Nikolaus Rath Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Dec 28 18:10:09 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cMHjo-0003Dm-7Q for ged-emacs-devel@m.gmane.org; Wed, 28 Dec 2016 18:10:04 +0100 Original-Received: from localhost ([::1]:60190 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cMHjt-0005dj-1D for ged-emacs-devel@m.gmane.org; Wed, 28 Dec 2016 12:10:09 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:54740) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cMHjh-0005ca-SX for emacs-devel@gnu.org; Wed, 28 Dec 2016 12:09:58 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cMHje-0002G1-Mz for emacs-devel@gnu.org; Wed, 28 Dec 2016 12:09:57 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:42133) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cMHje-0002Fo-J2; Wed, 28 Dec 2016 12:09:54 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:4008 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cMHjd-0000j3-S9; Wed, 28 Dec 2016 12:09:54 -0500 In-reply-to: <871swsf1es.fsf@thinkpad.rath.org> (message from Nikolaus Rath on Wed, 28 Dec 2016 08:45:15 -0800) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 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" Xref: news.gmane.org gmane.emacs.devel:210905 Archived-At: > From: Nikolaus Rath > Date: Wed, 28 Dec 2016 08:45:15 -0800 > > >> > I'm still wondering how useful this could be for C code though. There are > >> > many coding conventions where the opening { of a function does not go in > >> > the left-most column. As far as I understand, such coding conventions would > >> > lead to slower parsing? > >> > >> This convention is not useful for C. > > > > Our coding standards clearly call for starting a function's body with > > an opening brace in column zero. > > I would hope that Emacs is used not only to edit its own source code but > also other code, for which these standards don't apply. It is, but how is that relevant to the issue at hand? The issue at hand is how does open-paren-in-column-0-is-defun-start affect C code editing. The intent of my reference to GNU standards was to point out that having an opening brace in column zero is a very frequent situation in the C sources of any GNU project, and therefore saying this convention is not useful for C flies in the face of the reality right under our feet.