[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Font-lock decides function call is function declaration in C+ + - em
From: |
Alan Mackenzie |
Subject: |
Re: Font-lock decides function call is function declaration in C+ + - embryonic solution. |
Date: |
3 Mar 2007 11:18:36 +0100 |
Date: |
Sat, 3 Mar 2007 11:27:58 +0000 |
User-agent: |
Mutt/1.5.9i |
Hi, Chong and Richard!
On Thu, Mar 01, 2007 at 12:19:57PM -0500, Chong Yidong wrote:
> Hi Alan,
> Judging by the size of the patch you sent, and the time it's taking to
> write it, this seems to be a lot of work.
It's really not a big patch. It's lots of lines of lisp, yet it's mainly
straight through, top to bottom, without complicated loops, and the
functions it calls are almost entirely base Emacs functions.
I confess I got bogged down trying to write a general fix to the problem.
I've given that up for now. Sorry.
> Once we include the time necessary for testing such a big change, it
> will probably significantly delay the Emacs 22 release.
> In the interest of release Emacs 22 sometime in 2007, I'd like to
> suggest postphoning this fix to Emacs 23, and simply turning off
> variable-highlighting for C++ constructors.
> What do you think?
That turning off the highlighting would take longer to implement and
test. [BTW, I don't think it's connected with C++ constructors, unless
I've missed something - it's about removing type names from a cache when
those names cease to be types.]
I suggest instead that I tidy up that embryonic patch and commit it. I
think I'll be able to do this today or tomorrow. It will not fully
resolve the bug, but it will help.
#########################################################################
Simon's bug report also gave this "variation" of the bug:
int main() {
foo(fubar);
bar();
}
, where "bar" got fontified as a variable when the fragment is typed in
a certain way. This is actually a distinct bug, which I think will be
easier to fix.
--
Alan Mackenzie (Ittersbach, Germany).