GNU bug report logs - #62339
cc-mode fontifies variables incorrectly when const follows type

Previous Next

Full log

Message #20 received at 62339 <at> debbugs.gnu.org (full text, mbox):

From: Daniel Colascione <dancol <at> dancol.org>
To: Alan Mackenzie <acm <at> muc.de>
Cc: 62339 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#62339: cc-mode fontifies variables incorrectly when const
 follows type
Date: Wed, 22 Mar 2023 18:17:05 -0400

Alan Mackenzie <acm <at> muc.de> writes:

> Hello, Eli and Daniel.
>
> Thanks for the bug report!
>
> On Wed, Mar 22, 2023 at 17:12:52 +0200, Eli Zaretskii wrote:
>> > From: Daniel Colascione <dancol <at> dancol.org>
>> > Cc: 62339 <at> debbugs.gnu.org
>> > Date: Wed, 22 Mar 2023 10:19:55 -0400
>
>> > This problem reproduces for me on latest master with emacs -Q:
>
>> > ```
>> > TEST(Foo, Bar) {
>> >   NamedTemporaryDirectory const test_directory;
>> > }
>> > ```
>
>> Thanks.  What I see with Emacs built from master is that
>> test_directory in the above example gets font-lock-type-face in
>> c++-mode (but not in c-mode).  With Emacs built from emacs-29, both
>> modes produce correct fontification.
>
>> Alan, can you please look into this?
>
> I think this is caused by a faulty fix of bug #59267, where "typeless" C
> declarations like
>
>     const foo;
>
> , which are implicit int, were not being recognised.

Can we back out this fix in the meantime? These "typeless" declarations
can't be all that common.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.