From: Chong Yidong <cyd@stupidchicken.com>
To: "Marshall\, Simon" <simon.marshall@misys.com>
Cc: "'bug-cc-mode@gnu.org'" <bug-cc-mode@gnu.org>,
"'emacs-devel@gnu.org'" <emacs-devel@gnu.org>
Subject: Re: Font-lock decides function call is function declaration in C+ +
Date: Mon, 05 Feb 2007 12:14:48 -0500 [thread overview]
Message-ID: <87ps8ottkn.fsf@stupidchicken.com> (raw)
In-Reply-To: <81CCA6588E60BB42BE68BD029ED4826011AB3F79@wimex2.wim.midas-kapiti.com> (Simon Marshall's message of "Mon\, 5 Feb 2007 16\:46\:32 -0000")
"Marshall, Simon" <simon.marshall@misys.com> writes:
> emacs -Q foo.cpp
> int SPC main() SPC { RET } RET C-p C-o bar();
>
> OK so far. Now to insert the "foo();" line:
>
> C-a C-o foo
>
> At this point, "foo" is fontified as a type, and "bar" as a variable. OK.
> Now:
>
> ()
>
> The fontification of "foo" and "bar" disappears. OK. Now complete the
> snippet:
>
> ;
>
> Now "foo" is fontified as a variable. This is wrong.
I can reproduce this now. Note that it only happens in c++ mode, not
in plain c-mode.
Hopefully, someone familiar with the cc-mode code can debug it.
next prev parent reply other threads:[~2007-02-05 17:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-05 16:46 Font-lock decides function call is function declaration in C+ + Marshall, Simon
2007-02-05 17:14 ` Chong Yidong [this message]
2007-02-07 20:45 ` Alan Mackenzie
2007-02-09 21:25 ` Chong Yidong
2007-02-11 17:40 ` Alan Mackenzie
2007-02-11 20:11 ` Stefan Monnier
2007-02-11 23:18 ` Chong Yidong
2007-02-12 2:45 ` Stefan Monnier
2007-02-12 17:59 ` Alan Mackenzie
2007-02-22 23:47 ` Font-lock decides function call is function declaration in C+ + - embryonic solution Alan Mackenzie
2007-03-01 17:19 ` Chong Yidong
2007-03-02 3:28 ` Richard Stallman
2007-03-03 10:18 ` Alan Mackenzie
2007-03-08 22:07 ` Font-lock decides function call is function declaration in C+ + - Patch Alan Mackenzie
2007-03-08 22:58 ` Chong Yidong
2007-03-09 21:25 ` Richard Stallman
2007-03-09 23:23 ` Alan Mackenzie
2007-03-11 4:24 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2007-02-12 14:38 Font-lock decides function call is function declaration in C+ + Marshall, Simon
2007-02-12 15:53 ` Stuart D. Herring
2007-02-12 16:17 ` Stefan Monnier
2007-02-12 17:41 ` Alan Mackenzie
2007-02-12 18:06 ` Stuart D. Herring
2007-02-13 22:22 ` Alan Mackenzie
2007-02-09 10:32 Marshall, Simon
[not found] <81CCA6588E60BB42BE68BD029ED48260105584F1@wimex2.wim.midas-kapiti.com>
2007-02-02 4:04 ` Chong Yidong
2007-01-26 21:18 Tetris trademark Chip Coldwell
2007-01-27 4:19 ` Richard Stallman
2007-01-27 13:03 ` Chris Moore
2007-01-27 13:39 ` Alfred M. Szmidt
2007-01-28 19:54 ` Chong Yidong
2007-01-28 20:23 ` Alfred M. Szmidt
2007-01-28 21:34 ` Chong Yidong
2007-01-28 22:41 ` Alfred M. Szmidt
2007-01-29 0:54 ` Chris Moore
2007-02-02 23:57 ` Font-lock decides function call is function declaration in C+ + Chong Yidong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ps8ottkn.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=bug-cc-mode@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=simon.marshall@misys.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).