From: Eli Zaretskii <eliz@gnu.org>
To: John Yates <john@yates-sheets.org>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: etags failing with structure members
Date: Sat, 11 Mar 2017 18:37:37 +0200 [thread overview]
Message-ID: <83varfdb1q.fsf@gnu.org> (raw)
In-Reply-To: <CAJnXXogxTyPLzBD7vm3LhWOSSpmFE+TAcU7XtyNodxVzTT_vmA@mail.gmail.com> (message from John Yates on Sat, 11 Mar 2017 10:42:23 -0500)
> From: John Yates <john@yates-sheets.org>
> Date: Sat, 11 Mar 2017 10:42:23 -0500
> Cc: martin rudalics <rudalics@gmx.at>, Emacs developers <emacs-devel@gnu.org>
>
> On Sat, Mar 11, 2017 at 6:24 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > They look like a beginning of a K&R style function definition:
>
> For many contemporary codebases support for K&R is only a liability.
> Might it be possible to drop such support (at least optionally)?
Even if we'd decided to drop that (and I'm not so sure we should),
someone would still need to rework the humongous state machine in
C_entries and consider_token (which supports all C-like languages,
including C++, ObjC, Java, etc.) to get rid of that cleanly. If such
a volunteer steps forward, this question will become something we (and
the volunteer) should consider, yes. But until that time, simple
localized changes are all we can afford, unfortunately, at least as
long as I'm the only one who dares to touch etags bugs.
next prev parent reply other threads:[~2017-03-11 16:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 7:54 etags failing with structure members martin rudalics
2017-03-10 9:21 ` Eli Zaretskii
2017-03-11 10:27 ` martin rudalics
2017-03-11 11:24 ` Eli Zaretskii
2017-03-11 15:42 ` John Yates
2017-03-11 16:37 ` Eli Zaretskii [this message]
2017-03-12 14:27 ` Alan Mackenzie
2017-03-12 15:39 ` Eli Zaretskii
2017-03-12 18:03 ` martin rudalics
2017-03-12 18:09 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83varfdb1q.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.org \
--cc=rudalics@gmx.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.