From: "Marshall, Simon" <simon.marshall@misys.com>
To: "'Stefan Monnier'" <monnier@iro.umontreal.ca>,
"'Chong Yidong'" <cyd@stupidchicken.com>,
"'Alan Mackenzie'" <acm@muc.de>
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, 12 Feb 2007 14:38:59 -0000 [thread overview]
Message-ID: <81CCA6588E60BB42BE68BD029ED4826011ED2AA1@wimex2.wim.midas-kapiti.com> (raw)
> >> Once a variable has been inserted into c-found-types, it will stay
there
> >> almost for ever; it will stay there until re-fontification is done from
> >> BOB (I'm not sure whether or not that also means (point-min) on a
> >> narrowed buffer). This permanence seems to be the fundamental problem.
> >>
> >> I think a solution might be to remove "foo" from c-found-types whenever
> >> text is inserted/deleted in the vicinity of "foo\n bar ();" which
> >> syntactically destroys its status as a type identifier. I'll need to
> >> think a lot more about this.
>
> > For the Emacs 22 release, if no simple fix is forthcoming, could we
> > simply get font-lock to avoid higlighting constructor functions?
>
> Or to not try to auto-learn types,
Yes, unfortunately, I think that if you try to learn types on-the-fly then
you will always be vulnerable to this sort of problem. The issue is that
cc-mode needs to know as soon as a change invalidates it as a candidate type
(ie, deletion of some/all of the text "foo" or interruption of the
whitespace between "foo" and its candidate identifier "bar"). I can think
of a few ways you could attempt to do it, but they are a bit intensive and
far from simple.
Perhaps cc-mode should only try to learn types when fontifying the whole
buffer?
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.
next reply other threads:[~2007-02-12 14:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-12 14:38 Marshall, Simon [this message]
2007-02-12 15:53 ` Font-lock decides function call is function declaration in C+ + 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
-- strict thread matches above, loose matches on Subject: below --
2007-02-09 10:32 Marshall, Simon
2007-02-05 16:46 Marshall, Simon
2007-02-05 17:14 ` Chong Yidong
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
[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=81CCA6588E60BB42BE68BD029ED4826011ED2AA1@wimex2.wim.midas-kapiti.com \
--to=simon.marshall@misys.com \
--cc=acm@muc.de \
--cc=bug-cc-mode@gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).