From: Chong Yidong <cyd@stupidchicken.com>
To: emacs-devel@gnu.org
Subject: Re: Font-lock decides function call is function declaration in C+ + - embryonic solution.
Date: Thu, 01 Mar 2007 12:19:57 -0500 [thread overview]
Message-ID: <87y7mgubia.fsf@stupidchicken.com> (raw)
In-Reply-To: 20070223010309.GA3981@muc.de
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. 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?
next prev parent reply other threads:[~2007-03-01 17:19 UTC|newest]
Thread overview: 22+ 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
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 [this message]
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-23 10:23 Font-lock decides function call is function declaration in C+ + - embryonic solution Marshall, Simon
2007-02-23 21:01 ` Alan Mackenzie
2007-02-27 15:08 Marshall, Simon
2007-03-06 10:49 Marshall, Simon
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=87y7mgubia.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
/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).