From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "spamfilteraccount@gmail.com" Newsgroups: gmane.emacs.help Subject: Re: State-machine based syntax highlighting Date: 8 Dec 2006 00:36:50 -0800 Organization: http://groups.google.com Message-ID: <1165567010.036350.185800@n67g2000cwd.googlegroups.com> References: <1165472049.496117.320630@79g2000cws.googlegroups.com> <1165488825.132862.189340@79g2000cws.googlegroups.com> <1165492567.864982.59980@79g2000cws.googlegroups.com> <1165495364.560960.271250@f1g2000cwa.googlegroups.com> <1165501630.172348.157180@j72g2000cwa.googlegroups.com> <1165502373.932709.15860@79g2000cws.googlegroups.com> <1165510932.276718.251220@73g2000cwn.googlegroups.com> <1165516558.657188.21610@j44g2000cwa.googlegroups.com> <1165517838.526624.171950@f1g2000cwa.googlegroups.com> <1165563183.140436.326110@16g2000cwy.googlegroups.com> <87psaukdu1.fsf@lion.rapttech.com.au> NNTP-Posting-Host: dough.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Trace: sea.gmane.org 1165567513 25097 80.91.229.10 (8 Dec 2006 08:45:13 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 8 Dec 2006 08:45:13 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Fri Dec 08 09:45:11 2006 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by dough.gmane.org with esmtp (Exim 4.50) id 1GsbLr-0006CZ-EH for geh-help-gnu-emacs@m.gmane.org; Fri, 08 Dec 2006 09:45:03 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1GsbLq-0004Z4-Rl for geh-help-gnu-emacs@m.gmane.org; Fri, 08 Dec 2006 03:45:03 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!postnews.google.com!n67g2000cwd.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.help Original-Lines: 18 Original-NNTP-Posting-Host: 194.88.55.211 Original-X-Trace: posting.google.com 1165567016 13452 127.0.0.1 (8 Dec 2006 08:36:56 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Fri, 8 Dec 2006 08:36:56 +0000 (UTC) In-Reply-To: <87psaukdu1.fsf@lion.rapttech.com.au> User-Agent: G2/1.0 X-HTTP-UserAgent: Opera/9.00 (X11; Linux i686; U; en),gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: n67g2000cwd.googlegroups.com; posting-host=194.88.55.211; posting-account=b98TkQ0AAAD7PsllN8gfWGRoPOPWdnv4 Original-Xref: shelby.stanford.edu gnu.emacs.help:143741 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:39343 Archived-At: Tim X wrote: > > The problem with parse based analysis is that you need an in-built > parser for all the languages that the editor is used to develop in and > this is not a trivial task. I suspect some sort of plugin architecture > that is able to use stand-alone parses for some language of interest > would probably be the way to go as it is unlikely even a small subset > of the languages devleoped within an emacs environment can have a > parser developed in elisp which is readily maintained. I think too that some kind of bridge or plugin architecture is the answer. Lots of languages provide access to syntax trees in some form (python, java, etc.), so it would be much simpler to use their native implementation than reinveinting everything in elisp.