From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: joakim@verona.se Newsgroups: gmane.emacs.devel Subject: Re: "Font-lock is limited to text matching" is a myth Date: Tue, 11 Aug 2009 21:12:13 +0200 Message-ID: References: <7b501d5c0908091634ndfba631vd9db6502db301097@mail.gmail.com> <1249942011.29022.15.camel@projectile.siege-engine.com> <1249955428.29022.186.camel@projectile.siege-engine.com> <9c768dc60908102347v57bdf38ara9fe2179f68c07e4@mail.gmail.com> <42D4C5C5-E702-4E30-AB95-A016280F20C7@merrillpress.com> <87r5vi2ym7.fsf@stupidchicken.com> <31BA527B-46FC-400C-A2B1-8D4A87293C19@merrillpress.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1250017967 10903 80.91.229.12 (11 Aug 2009 19:12:47 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 11 Aug 2009 19:12:47 +0000 (UTC) Cc: Daniel Colascione , David Engster , Daniel Colascione , Chong Yidong , Deniz Dogan , Stefan Monnier , emacs-devel@gnu.org, Steve Yegge , Leo , Miles Bader To: Lennart Borgman Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 11 21:12:39 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1Mawlw-0007Sm-LJ for ged-emacs-devel@m.gmane.org; Tue, 11 Aug 2009 21:12:36 +0200 Original-Received: from localhost ([127.0.0.1]:56981 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mawlu-0000qZ-V0 for ged-emacs-devel@m.gmane.org; Tue, 11 Aug 2009 15:12:35 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mawll-0000o9-O4 for emacs-devel@gnu.org; Tue, 11 Aug 2009 15:12:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mawlh-0000mB-61 for emacs-devel@gnu.org; Tue, 11 Aug 2009 15:12:25 -0400 Original-Received: from [199.232.76.173] (port=45457 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mawlh-0000m5-02 for emacs-devel@gnu.org; Tue, 11 Aug 2009 15:12:21 -0400 Original-Received: from iwfs.imcode.com ([82.115.149.64]:50815 helo=gate.verona.se) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mawle-0006bf-C0; Tue, 11 Aug 2009 15:12:18 -0400 Original-Received: from localhost.localdomain (IDENT:1005@localhost [127.0.0.1]) by gate.verona.se (8.13.4/8.11.4) with ESMTP id n7BJCDfR006946; Tue, 11 Aug 2009 21:12:13 +0200 In-Reply-To: (Lennart Borgman's message of "Tue, 11 Aug 2009 20:08:52 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.50 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:114092 Archived-At: Lennart Borgman writes: > On Tue, Aug 11, 2009 at 8:04 PM, wrote: >> Daniel Colascione writes: >> >> >>> - full parsers belong in the CEDET infrastructure where they can be >>> accessed via a common API >>> - if this API is not rich enough, it ought to be extended >>> - normal major modes shouldn't rely on rigid grammars because that >>> makes them brittle. Anything that needs such a grammar should be an >>> optional and preferably generic minor-mode >>> >>> (I still think it'd be worthwhile to include the JS2 parser in CEDET, >>> which supports parsers not necessarily generated with wisent or bison. >>> It seems robust in its problem domain.) >> >> Small piece of information: CEDET already includes a Javascript parser >> that I provided some time ago. > > > What benefits do the different approaches (your CEDET Semantic > Javascript parser and JS2, maybe also a theoretical sub-process rhino > (or similar) parser) have? I havent looked into what JS2 does. Cedet provides interfaces to hook in parsers of varying kinds. If you use this interface, you are a cedet parser, and you get the benefits that all the cedet tools work: semantic navigation etc. currently there are no sub-process parsers implemeted AFAIK, but there are sub-process tag generators. > -- Joakim Verona