From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: 61403@debbugs.gnu.org, casouri@gmail.com
Subject: bug#61403: 30.0.50; C tree-sitter bug?
Date: Sun, 12 Feb 2023 16:36:43 +0200 [thread overview]
Message-ID: <83h6vrgdc4.fsf@gnu.org> (raw)
In-Reply-To: <87fsbbynur.fsf@yahoo.com> (message from Po Lu on Sun, 12 Feb 2023 22:12:12 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: casouri@gmail.com, 61403@debbugs.gnu.org
> Date: Sun, 12 Feb 2023 22:12:12 +0800
>
> static char *
> foo (void)
> {
>
> }
>
> ANSI C states that ``static'' is a storage class specifier, not a type
> specifier or qualifier, definitely not part of the type, which is ``char
> *''.
>
> CC Mode normally fontifies this accordingly, in font-lock-keyword-face.
Only for types qualifiers it knows about. There are a lot of examples
in w32*.c files, here's one (fron line 610 of w32.c):
static BOOL WINAPI
open_process_token (HANDLE ProcessHandle,
DWORD DesiredAccess,
PHANDLE TokenHandle)
I think we are splitting hair here. In the code snippet you posted in
the OP, the non-fontification of 'char' is the only real issue.
prev parent reply other threads:[~2023-02-12 14:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h6vt364d.fsf.ref@yahoo.com>
2023-02-10 15:14 ` bug#61403: 30.0.50; C tree-sitter bug? Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-12 8:27 ` Yuan Fu
2023-02-12 8:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-12 8:56 ` Eli Zaretskii
2023-02-12 10:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-12 12:31 ` Eli Zaretskii
2023-02-12 12:36 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-12 13:04 ` Eli Zaretskii
2023-02-12 14:12 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-02-12 14:36 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h6vrgdc4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=61403@debbugs.gnu.org \
--cc=casouri@gmail.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).