[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#64204: C/C++ local variables not syntax highlighted if they start wi
From: |
Alan Mackenzie |
Subject: |
bug#64204: C/C++ local variables not syntax highlighted if they start with $ |
Date: |
Thu, 22 Jun 2023 12:33:13 +0000 |
Hello, Eli.
On Thu, Jun 22, 2023 at 13:13:59 +0300, Eli Zaretskii wrote:
> > Date: Thu, 22 Jun 2023 09:11:38 +0000
> > Cc: luangruo@yahoo.com, 64204@debbugs.gnu.org
> > From: Alan Mackenzie <acm@muc.de>
> > > Thanks, but shouldn't this be optional behavior, which users should be
> > > able to control? Standard C disallows '$' in identifiers AFAIK, and
> > > some users might wish to follow the Standard.
> > The thing is, such an option would be difficult to implement. At the
> > moment, c-symbol-start and c-symbol-key (regular expressions which match
> > the start of an identifier and all of one) are calculated in cc-langs.el
> > at compilation time. They are widely used (~40 times) in the indentation
> > engine and fontification.
> > It would be necessary to change these constants to variables, probably
> > doubling the number of relevant c-lang-const's in cc-langs.el, and to add
> > a mechanism to toggle between them at run time.
> > I don't feel that the benefit from this new option would really be worth
> > the work it would take to implement.
> I do feel it's worth the effort. If we value correct fontification,
> of course. I don't know what my opinions on this mean for you, but
> there you have it. I cannot force you make this change, of course, I
> can only try to convince.
Having thought about this some more, maybe it's not such a big problem.
The strategy I'm thinking about would not attempt to analyse identifiers
with $ in them. Instead, it would amend only the fontification, with a
new ad-hoc entry in font-lock-keywords which would go over all
identifiers at the end of the fontification, and splat those containing a
$ with font-lock-warning-face.
I can see more problems arising when people start wanting to use
identifiers with random Unicode characters in them. :-(
--
Alan Mackenzie (Nuremberg, Germany).
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, (continued)
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Eli Zaretskii, 2023/06/22
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Po Lu, 2023/06/22
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Eli Zaretskii, 2023/06/22
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Po Lu, 2023/06/22
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Eli Zaretskii, 2023/06/22
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Po Lu, 2023/06/22
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Eli Zaretskii, 2023/06/22
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Po Lu, 2023/06/22
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Alan Mackenzie, 2023/06/22
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Eli Zaretskii, 2023/06/22
- bug#64204: C/C++ local variables not syntax highlighted if they start with $,
Alan Mackenzie <=
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Alan Mackenzie, 2023/06/28
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Eli Zaretskii, 2023/06/28
- bug#64204: C/C++ local variables not syntax highlighted if they start with $, Joseph Garvin, 2023/06/29