From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel@gnu.org
Subject: Re: Help etags parse lisp.j
Date: Mon, 21 Mar 2016 10:40:20 -0700 [thread overview]
Message-ID: <56F03204.9000701@cs.ucla.edu> (raw)
In-Reply-To: <83vb4f6bs7.fsf@gnu.org>
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.
> . 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.
next prev parent reply other threads:[~2016-03-21 17:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 17:19 Help etags parse lisp.j Eli Zaretskii
2016-03-20 17:34 ` Andreas Schwab
2016-03-20 17:59 ` Eli Zaretskii
2016-03-20 18:11 ` Help etags parse lisp.h Eli Zaretskii
2016-03-21 7:54 ` Help etags parse lisp.j Paul Eggert
2016-03-21 10:58 ` Andreas Schwab
2016-03-21 16:10 ` Eli Zaretskii
2016-03-22 12:46 ` Stefan Monnier
2016-03-22 16:24 ` Eli Zaretskii
2016-03-21 13:40 ` Stefan Monnier
2016-03-21 16:22 ` Eli Zaretskii
2016-03-21 17:40 ` Paul Eggert [this message]
2016-03-21 18:13 ` Eli Zaretskii
2016-03-21 21:28 ` John Wiegley
2016-03-22 12:25 ` Stefan Monnier
2016-03-21 18:10 ` Stefan Monnier
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=56F03204.9000701@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.