From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.cc-mode.general,gmane.emacs.devel Subject: Re: [sigra@home.se: C++-mode: Syntax highlighting: wrong color for function identifier depending on the kind of whitespace that follows] Date: Thu, 16 Feb 2006 18:21:07 +0100 Message-ID: <43F4B483.1050800@gmx.at> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1140110597 14811 80.91.229.2 (16 Feb 2006 17:23:17 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Thu, 16 Feb 2006 17:23:17 +0000 (UTC) Cc: Ralf Angeli , bug-cc-mode@gnu.org, Stefan Monnier , rms@gnu.org, emacs-devel@gnu.org Original-X-From: cc-mode-help-admin@lists.sourceforge.net Thu Feb 16 18:23:12 2006 Return-path: Envelope-to: sf-cc-mode-help@m.gmane.org Original-Received: from lists-outbound.sourceforge.net ([66.35.250.225]) by ciao.gmane.org with esmtp (Exim 4.43) id 1F9mqP-0006l1-GA for sf-cc-mode-help@m.gmane.org; Thu, 16 Feb 2006 18:23:05 +0100 Original-Received: from sc8-sf-list1-b.sourceforge.net (sc8-sf-list1-b.sourceforge.net [10.3.1.7]) by sc8-sf-spam2.sourceforge.net (Postfix) with ESMTP id 1CE4F1249A; Thu, 16 Feb 2006 09:23:04 -0800 (PST) Original-Received: from sc8-sf-mx2-b.sourceforge.net ([10.3.1.92] helo=mail.sourceforge.net) by sc8-sf-list1.sourceforge.net with esmtp (Exim 4.30) id 1F9mpZ-0007bx-Tr for cc-mode-help@lists.sourceforge.net; Thu, 16 Feb 2006 09:22:13 -0800 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by mail.sourceforge.net with esmtps (TLSv1:RC4-SHA:128) (Exim 4.44) id 1F9mpY-0000Ye-6t for cc-mode-help@lists.sourceforge.net; Thu, 16 Feb 2006 09:22:13 -0800 Original-Received: from monty-python.gnu.org ([199.232.76.173]) by fencepost.gnu.org with esmtp (Exim 4.34) id 1F9mpW-0002EL-V3 for bug-cc-mode@gnu.org; Thu, 16 Feb 2006 12:22:10 -0500 Original-Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.52) id 1F9mud-00089M-UQ for bug-cc-mode@gnu.org; Thu, 16 Feb 2006 12:27:30 -0500 Original-Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.52) id 1F9mud-00088c-Cm for bug-cc-mode@gnu.org; Thu, 16 Feb 2006 12:27:27 -0500 Original-Received: (qmail invoked by alias); 16 Feb 2006 17:21:59 -0000 Original-Received: from N896P018.adsl.highway.telekom.at (EHLO [62.47.55.242]) [62.47.55.242] by mail.gmx.net (mp029) with SMTP; 16 Feb 2006 18:21:59 +0100 X-Authenticated: #14592706 User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en Original-To: Alan Mackenzie In-Reply-To: X-Y-GMX-Trusted: 0 X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by sourceforge.net. See http://spamassassin.org/tag/ for more details. Report problems to http://sf.net/tracker/?func=add&group_id=1&atid=200001 1.0 FORGED_RCVD_HELO Received: contains a forged HELO Original-Sender: cc-mode-help-admin@lists.sourceforge.net Errors-To: cc-mode-help-admin@lists.sourceforge.net X-BeenThere: cc-mode-help@lists.sourceforge.net X-Mailman-Version: 2.0.9-sf.net Precedence: bulk List-Unsubscribe: , List-Id: Bug reports, feature requests, and general talk about CC Mode. List-Post: List-Help: List-Subscribe: , List-Archive: X-Original-Date: Thu, 16 Feb 2006 18:21:07 +0100 Xref: news.gmane.org gmane.emacs.cc-mode.general:3037 gmane.emacs.devel:50621 Archived-At: > There's a fundamental mismatch between Font Lock's implementation and > reality: Font Lock assumes that, with the exception of comments and > strings, the fontification of a region is dependent only on text near the > region. This works pretty well for programming languages, but badly for > mark-up languages. Font Lock is not to blame here, you must improve `parse-partial-sexp'. The following comment in font-lock has been here ever since ... "Perhaps one day someone will write some syntactic parsers for common languages and a son-of-font-lock.el could use them rather then relying so heavily on the keyword (regexp) pass." > I am convinced that, in the long term, we need an analogous, fast, global > mechanism for for locating and characterizing regions bounded by > arbitrary delimiters - in this case "<<" and ">>", but could just as well > be Texinfo's "{" and "}" or Lex's and Yacc's "%{", "%}" and "%%" or > "literate programing"'s boundaries between narrative text and executable > code, or "here documents" within a shell script. > > Until we have this, I think we'll be entangling ourselves in an ever > stickier web of ad-hoc workarounds. In the short term, such mechanisms needn't even be fast. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642