[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+ +
From: |
Chong Yidong |
Subject: |
Re: Font-lock decides function call is function declaration in C+ + |
Date: |
Thu, 01 Feb 2007 23:04:48 -0500 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.93 (gnu/linux) |
Does this bug still exist with latest CVS? If so, please provide a
simple test case (I couldn't find one in your previous messages).
> Hi, this bug remains[*] and a quick look at the C++ file I am editing shows
> that most of my methods have ended up with this sort of misfontification
> somewhere. Note that misfontification does not occur during initial
> fontification, only after editing (though not in a way I can replicate). I
> guess sometimes it thinks function calls are part of a declaration, though it
> doesn't necessarily happen when the preceding statement is a declaration. In
> one occurrence in my C++ file, the misfontification has occurred immediately
> after a for loop.
>
> Again, I'm asking for help. I never got a response last time. What do I need
> to look at to see what is going on?
>
> [*] following my revision 1.18 date: 2006-11-15 16:31:03 fix in cc-fonts.el of
> another unrelated issue in CVS Emacs, Emacs CVS fontifies the below with
> font-lock-variable-name-face, rather than font-lock-function-name-face, which
> may/may not give a pointer to where the problem lies.
>
> _____________________________________________
> From: Marshall, Simon
> Sent: 07 September 2006 17:41
> To: 'address@hidden'
> Cc: 'address@hidden'
> Subject: Font-lock decides function call is function declaration in
> C++
>
> Intermittently, but for ages, Emacs CVS suddenly decides that C++ lines of
> code of the form:
>
> foo(bar);
>
> Or:
>
> foo() = bar;
>
> Are function declarations, and puts font-lock-function-name-face on (in
> these examples) "foo". It seems to happen when I am editing the line in
> question, or maybe just on a line near it. (I think the last time it
> appeared when I did M-^ on the line following, but I could be wrong.
> There
> is nothing wrong with the code preceding the misfontification.)
>
> Editing the line or lines above it do not make the fontification
> permanently go away. For example, if I comment out all preceding lines,
> the fontification is removed. However, when I remove the comments, it
> comes back. The only way I've found to get rid of it is to turn
> font-lock-mode off and on.
>
> It's driving me mad because I can't work out what, in terms of the code
> preceding it, is causing it to fontify in this way. In one case, the
> function call was the first statement in the method, and I noticed that
> the
> text also had the "c-in-sws" property (as well as the "face" property).
> Debugging through cc-engine.el doesn't look fun and I don't know if the
> presence of this property is a red herring.
>
> I can't reproduce it, so I'm really asking for help. Any ideas? What can
> I do to work out what is going wrong?
>
> Simon.
>
>
>
> This email message is intended for the named recipient only. It may be
> privileged and/or confidential. If you are not the named recipient of this
> email please notify us immediately and do not copy it or use it for any
> purpose, nor disclose its contents to any other person.
>
>
>
> Misys Banking Systems is a trading name of Misys International Banking Systems
> Limited which is registered in England and Wales under company registration
> number 00971479 and with its registered office address at Burleigh House,
> Chapel Oak, Salford Priors, Evesham WR11 8SP.
>
>
>
> THIS E-MAIL DOES NOT CONSTITUTE THE COMMENCEMENT OF LEGAL RELATIONS BETWEEN
> YOU
> AND MISYS INTERNATIONAL BANKING SYSTEMS LIMITED. PLEASE REFER TO THE EXECUTED
> CONTRACT BETWEEN YOU AND THE RELEVANT MEMBER OF THE MISYS GROUP FOR THE
> IDENTITY OF THE CONTRACTING PARTY WITH WHICH YOU ARE DEALING.
>
> _______________________________________________
> emacs-pretest-bug mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
- Re: Font-lock decides function call is function declaration in C+ +, (continued)
- Re: Font-lock decides function call is function declaration in C+ +, Chong Yidong, 2007/02/05
- Re: Font-lock decides function call is function declaration in C+ +, Alan Mackenzie, 2007/02/07
- Re: Font-lock decides function call is function declaration in C+ +, Chong Yidong, 2007/02/09
- Re: Font-lock decides function call is function declaration in C+ +, Alan Mackenzie, 2007/02/11
- Re: Font-lock decides function call is function declaration in C+ +, Stefan Monnier, 2007/02/11
- Re: Font-lock decides function call is function declaration in C+ +, Chong Yidong, 2007/02/11
- Re: Font-lock decides function call is function declaration in C+ +, Stefan Monnier, 2007/02/11
- Re: Font-lock decides function call is function declaration in C+ +, Alan Mackenzie, 2007/02/12
Re: Font-lock decides function call is function declaration in C+ + - embryonic solution., Alan Mackenzie, 2007/02/22
RE: Font-lock decides function call is function declaration in C+ +, Marshall, Simon, 2007/02/09
Re: Font-lock decides function call is function declaration in C+ +,
Chong Yidong <=
RE: Font-lock decides function call is function declaration in C+ +, Marshall, Simon, 2007/02/12