[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: |
Stuart D. Herring |
Subject: |
Re: Font-lock decides function call is function declaration in C+ + |
Date: |
Mon, 12 Feb 2007 10:06:22 -0800 (PST) |
User-agent: |
SquirrelMail/1.4.8-2.el3.7lanl |
>> It's worse than that. Inserting a new letter that changes "foo", ...
>
> is taken care of, in the commonest case. When you type the "l" after
> "foo", this replaces "foo" with "fool" in the cache c-found-types.
Perhaps the cache should note how many times something is used? Then the
relatively common case of
socket s;
socket_factory sf/*=...*/;
s.initializeFrom(sf);
would not remove `socket' from the cache, but typo-corrections can still
change it.
Davis
--
This product is sold by volume, not by mass. If it appears too dense or
too sparse, it is because mass-energy conversion has occurred during
shipping.
- Re: Font-lock decides function call is function declaration in C+ +, (continued)
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, 2007/02/11
RE: Font-lock decides function call is function declaration in C+ +, Marshall, Simon, 2007/02/12