|
From: | Paul Eggert |
Subject: | Re: Help etags parse lisp.j |
Date: | Mon, 21 Mar 2016 10:40:20 -0700 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 |
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.
[Prev in Thread] | Current Thread | [Next in Thread] |