From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Help etags parse lisp.j Date: Mon, 21 Mar 2016 20:13:40 +0200 Message-ID: <83mvpr66nf.fsf@gnu.org> References: <83fuvl6p97.fsf@gnu.org> <87k2kxuk8i.fsf@linux-m68k.org> <83a8lt6nen.fsf@gnu.org> <83vb4f6bs7.fsf@gnu.org> <56F03204.9000701@cs.ucla.edu> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1458584067 25470 80.91.229.3 (21 Mar 2016 18:14:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 21 Mar 2016 18:14:27 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Paul Eggert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Mar 21 19:14:12 2016 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 1ai4LD-0003W1-OZ for ged-emacs-devel@m.gmane.org; Mon, 21 Mar 2016 19:14:11 +0100 Original-Received: from localhost ([::1]:59618 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ai4LC-0006Xm-RO for ged-emacs-devel@m.gmane.org; Mon, 21 Mar 2016 14:14:10 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:39990) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ai4L9-0006Wy-KG for emacs-devel@gnu.org; Mon, 21 Mar 2016 14:14:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ai4L5-00060E-0x for emacs-devel@gnu.org; Mon, 21 Mar 2016 14:14:07 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:32996) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ai4L4-00060A-Tw; Mon, 21 Mar 2016 14:14:02 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3023 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1ai4L3-0002NS-Vr; Mon, 21 Mar 2016 14:14:02 -0400 In-reply-to: <56F03204.9000701@cs.ucla.edu> (message from Paul Eggert on Mon, 21 Mar 2016 10:40:20 -0700) 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.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:202020 Archived-At: > Cc: emacs-devel@gnu.org > From: Paul Eggert > Date: Mon, 21 Mar 2016 10:40:20 -0700 > > Eli Zaretskii wrote: > > . in a large enough project, the user doesn't have an easy way of > > knowing whether she needs K&R support > > Yes they do. Any current project won't bother with K&R. The handful of older > projects that still have K&R and haven't bothered to rip it out (e.g., glibc is > *still* ripping it out) should have a toolsmith that knows ancient history. > Really, K&R support should be turned off by default. I don't want to turn it off, sorry. Etags is part of the set of tools that are invaluable when you are assigned with a task of making some change in a large project that lay dormant for years -- they allow you to quickly find your way in unfamiliar code. It should support old code styles. > > . implementing such an option is not trivial, to say the least, given > > the complex state machines used by parsing of C-like languages > > Nontrivial yes, but still it's not terribly hard. > > In the short term, perhaps we could work around the problem by replacing this: > > extern int make_ctrl_char (int) ATTRIBUTE_CONST; > > with this: > > extern ATTRIBUTE_CONST int make_ctrl_char (int); > > and similarly for the other affected declarations. Let me first see if I can find a better solution. Thanks.