From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Daniel Colascione <dancol@dancol.org>
Cc: 62339@debbugs.gnu.org, Alan Mackenzie <acm@muc.de>,
Eli Zaretskii <eliz@gnu.org>
Subject: bug#62339: cc-mode fontifies variables incorrectly when const follows type
Date: Thu, 23 Mar 2023 13:45:21 +0800 [thread overview]
Message-ID: <87r0tgxbpq.fsf@yahoo.com> (raw)
In-Reply-To: <1870c33ebb0.2829.cc5b3318d7e9908e2c46732289705cb0@dancol.org> (Daniel Colascione's message of "Wed, 22 Mar 2023 22:02:22 -0400")
Daniel Colascione <dancol@dancol.org> writes:
> Yes, we can We lived with the old behavior for decades. We can live with it a few weeks longer.
I reported this bug because I saw such code in use.
> Give me a break. No, you don't.
I do. I *see* code making use of implicit int every day.
> Practically nobody uses this obscure and deprecated C feature. If
> people did, we'd have addressed the problem years ago.
Who does ``we'' refer to?
Put bluntly, you have no right to decide what C code I see or write, or
what C code Alan wants to support. Declarations consisting of only a
storage class specifier are part of the 1989 C Standard.
This bug is no more important than bug#59267, and both will have to be
fixed and stay fixed.
next prev parent reply other threads:[~2023-03-23 5:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 15:14 bug#62339: cc-mode fontifies variables incorrectly when const follows type Daniel Colascione
2023-03-21 17:39 ` Eli Zaretskii
2023-03-22 14:19 ` Daniel Colascione
2023-03-22 15:12 ` Eli Zaretskii
2023-03-22 22:14 ` Alan Mackenzie
2023-03-22 22:17 ` Daniel Colascione
2023-03-23 0:42 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-23 2:02 ` Daniel Colascione
2023-03-23 5:45 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-03-23 7:22 ` Eli Zaretskii
2023-03-23 14:40 ` Alan Mackenzie
2023-04-05 15:53 ` Alan Mackenzie
2023-04-06 3:16 ` Daniel Colascione
2023-04-06 9:26 ` Alan Mackenzie
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=87r0tgxbpq.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=62339@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=dancol@dancol.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
/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.