Re: CC Mode troubles and Emacs 29

[Alan Mackenzie]

Hello, Eli.

On Tue, Jan 10, 2023 at 14:57:04 +0200, Eli Zaretskii wrote:
> > From: Po Lu <luangruo@yahoo.com>
> > Cc: Alan Mackenzie <acm@muc.de>,  emacs-devel@gnu.org
> > Date: Tue, 10 Jan 2023 09:05:36 +0800

> > Eli Zaretskii <eliz@gnu.org> writes:

> > >> Date: Mon, 9 Jan 2023 15:48:12 +0000
> > >> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
> > >> From: Alan Mackenzie <acm@muc.de>

[ .... ]

> > >> One of the bugs is bug #59671.

[ .... ]

> > That's just one bug of many.  If you look at the CC Mode bug tracker for
> > November, you'll see a lot of bugs that boil down to this: after 25 to
> > 60 minutes of editing in a buffer, the entire buffer is filled with
> > green splotches (making fontification useless) and C Mode has to be
> > re-enabled, because CC Mode keeps misrecognizing and fontifying
> > identifiers as types.

> If this is so, I find it strange that we don't have heaps of bug
> reports about this in our bug tracker.

We do have such heaps, where "this" is understood to be about the
fontification bugs, one of which Gregory accurately summarised.

Some of these bugs are 58534, 58537, 58795, 58796, 58772, 58883, 59032,
59070, 59233, 59267, 59051, 59427, which have all been fixed.
Additionally there are 59234, 59671 (the bug mentioned earlier) for which
patches are available but not yet committed, and 59216, for  which there
is, as yet, no patch.

> I doubt that anyone could ignore the terrible misbehavior you describe,
> if indeed the description is accurate and not exaggerated.

I don't think there was exaggeration, here.

> I guess we will have to wait till the pretest to see how bad that is
> in practice.

Why shouldn't I fix it before the pretest?  As mentioned above, the patch
is available.

-- 
Alan Mackenzie (Nuremberg, Germany).