From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [SPAM UNSURE] Maybe we're taking a wrong approach towards tree-sitter Date: Wed, 28 Jul 2021 16:27:26 +0300 Message-ID: <83lf5qtvpd.fsf@gnu.org> References: <8735rzyzbz.fsf@163.com> <86v94v3xh9.fsf@stephe-leake.org> <87wnpargnb.fsf@elite.giraud> <87h7gey7zx.fsf@163.com> <83pmv2twrl.fsf@gnu.org> <875ywuvauv.fsf@163.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26023"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stephen_leake@stephe-leake.org, manuel@ledu-giraud.fr, emacs-devel@gnu.org To: Andrei Kuznetsov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Jul 28 15:28:28 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1m8jbm-0006bL-VN for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Jul 2021 15:28:26 +0200 Original-Received: from localhost ([::1]:54754 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m8jbl-0002hH-LD for ged-emacs-devel@m.gmane-mx.org; Wed, 28 Jul 2021 09:28:25 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47236) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m8jav-0001PP-Gk for emacs-devel@gnu.org; Wed, 28 Jul 2021 09:27:33 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:54380) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m8jat-00008F-C6; Wed, 28 Jul 2021 09:27:31 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4673 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m8jas-0007cE-W5; Wed, 28 Jul 2021 09:27:31 -0400 In-Reply-To: <875ywuvauv.fsf@163.com> (message from Andrei Kuznetsov on Wed, 28 Jul 2021 21:14:48 +0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:271738 Archived-At: > From: Andrei Kuznetsov > Cc: manuel@ledu-giraud.fr, stephen_leake@stephe-leake.org, > emacs-devel@gnu.org > Date: Wed, 28 Jul 2021 21:14:48 +0800 > > Eli Zaretskii writes: > > > TS's code is written in plain C, and doesn't require any regeneration > > or source modifications. Anything else is misunderstanding. > > I am confused by TS's documentation, but if my understanding is correct, > shouldn't it be a parser generator that generates C code? TS is not a parser generator, it's a parser that accepts the language grammar from external files. > In that case, how would users load new parsers or modify existing > ones? If you want to modify a TS grammar file, you can (not in C). But why would you want to? The whole point of using TS is NOT to require that the Emacs development team or Emacs users should know enough about parsing of the many languages Emacs supports to modify the grammar. We want another, independent development team to take care of that, and we want to use the results of their development with minimum fuss. Exactly like we do with other libraries developed by other projects: the image libraries, GnuTLS, HarfBuzz, etc.