From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Dynamic loading progress Date: Sat, 14 Feb 2015 18:45:14 +0200 Message-ID: <83k2zkwig5.fsf@gnu.org> References: <83y4oiiw81.fsf@gnu.org> <838ugdf251.fsf@gnu.org> <54D80098.3020209@cs.ucla.edu> <54D85304.1030600@cs.ucla.edu> <54D9AC29.2020603@cs.ucla.edu> <54DA8539.1020905@cs.ucla.edu> <87zj8ktq8f.fsf@lifelogs.com> <54DD6413.1000403@cs.ucla.edu> <83wq3m436s.fsf@gnu.org> <54DDEB4D.5040300@dancol> <83egpt4zz6.fsf@gnu.org> <54DE12E9.5040606@dancol.org> <85twypiiug.fsf@stephe-leake.org> <83zj8g3n16.fsf@gnu.org> <857fvkik49.fsf@stephe-leake.org> <83lhk0wkfl.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1423932339 16472 80.91.229.3 (14 Feb 2015 16:45:39 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 14 Feb 2015 16:45:39 +0000 (UTC) Cc: emacs-devel@gnu.org To: stephen_leake@stephe-leake.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Feb 14 17:45:30 2015 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YMfqT-0000Dq-DN for ged-emacs-devel@m.gmane.org; Sat, 14 Feb 2015 17:45:29 +0100 Original-Received: from localhost ([::1]:60336 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMfqS-0000cR-Mx for ged-emacs-devel@m.gmane.org; Sat, 14 Feb 2015 11:45:28 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59592) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMfqL-0000bM-C6 for emacs-devel@gnu.org; Sat, 14 Feb 2015 11:45:26 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YMfqG-0007EJ-LU for emacs-devel@gnu.org; Sat, 14 Feb 2015 11:45:21 -0500 Original-Received: from mtaout25.012.net.il ([80.179.55.181]:43503) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YMfqG-0007E4-8R for emacs-devel@gnu.org; Sat, 14 Feb 2015 11:45:16 -0500 Original-Received: from conversion-daemon.mtaout25.012.net.il by mtaout25.012.net.il (HyperSendmail v2007.08) id <0NJR00M00SINOM00@mtaout25.012.net.il> for emacs-devel@gnu.org; Sat, 14 Feb 2015 18:40:00 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout25.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NJR00BQUSYOVSA0@mtaout25.012.net.il>; Sat, 14 Feb 2015 18:40:00 +0200 (IST) In-reply-to: <83lhk0wkfl.fsf@gnu.org> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:183066 Archived-At: > Date: Sat, 14 Feb 2015 18:02:22 +0200 > From: Eli Zaretskii > Cc: emacs-devel@gnu.org > > > From: Stephen Leake > > Date: Sat, 14 Feb 2015 09:32:54 -0600 > > > > Emacs ada-mode does indentation in two steps; first it parses the source > > code, and the parser actions are lisp functions that eventually call > > put-text-property to store information about the syntax and/or semantics > > on many identifiers. Then the indentation code uses those text > > properties to compute indentation. > > > > I have a generalized LALR parser implemented in elisp that is fast > > enough for many user's Ada files, but some users have much bigger files, > > and it takes them 10 seconds to parse. So I need a faster > > implementation. So far my benchmarking says I can get close with a > > machine compiled parser. > > > > So the module would contain the generalized LALR parser; the actions of > > the parser would still be calls to the lisp functions. > > But this means your mode is in Lisp to begin with, and it just calls > functions implemented in C to work faster. So you could leave the > calls to put-text-property in Lisp, and have the functions implemented > in the module return the information required to compute the arguments > to put-text-property. Or am I missing something? And btw, what exactly do you mean by "call Lisp" in this case? Call put-text-property, which is implemented in C in its entirety, doesn't constitute a call to Lisp in my book. Of course, that means we will want to export Fput_text_property...