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: How to add pseudo vector types Date: Sat, 24 Jul 2021 21:21:27 +0300 Message-ID: <83im0zy3mg.fsf@gnu.org> References: <83h7gw6pyj.fsf@gnu.org> <45EBF16A-C953-42C7-97D1-3A2BFEF7DD01@gmail.com> <83y2a764oy.fsf@gnu.org> <83v95b60fn.fsf@gnu.org> <00DD5BFE-D14E-449A-9319-E7B725DEBFB3@gmail.com> <83r1fz5xr9.fsf@gnu.org> <1AAB1BCC-362B-4249-B785-4E0530E15C60@gmail.com> <83czri67h0.fsf@gnu.org> <46BBFF88-76C3-4818-8805-5437409BEA93@gmail.com> <83wnpq46uk.fsf@gnu.org> <533BD53B-4E85-4E9E-B46A-346A5BBAD0F5@gmail.com> <258CB68D-1CC1-42C8-BDCD-2A8A8099B783@gmail.com> <1a776770-50b7-93cd-6591-c9a5b3a56eb8@gmail.com> <8335s64v10.fsf@gnu.org> <5380C92B-6C15-4490-A1E0-1C3132DBB16A@gmail.com> <83k0li2shw.fsf@gnu.org> <83eebq2mpy.fsf@gnu.org> <83lf5w26e3.fsf@gnu.org> <838s1vzp9i.fsf@gnu.org> <83pmv7y6fx.fsf@gnu.org> <83lf5vy58h.fsf@gnu.org> <2EB55126-2CEF-41A7-B5EF-4C3BDF21A034@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36838"; mail-complaints-to="usenet@ciao.gmane.io" Cc: cpitclaudel@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Yuan Fu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Jul 24 20:22:15 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 1m7MHv-0009OJ-G9 for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Jul 2021 20:22:15 +0200 Original-Received: from localhost ([::1]:42454 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m7MHu-0000kb-78 for ged-emacs-devel@m.gmane-mx.org; Sat, 24 Jul 2021 14:22:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42932) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7MHO-0008U4-FI for emacs-devel@gnu.org; Sat, 24 Jul 2021 14:21:42 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47696) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m7MHN-0008V7-0A; Sat, 24 Jul 2021 14:21:41 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3442 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 1m7MHM-000404-Jg; Sat, 24 Jul 2021 14:21:40 -0400 In-Reply-To: <2EB55126-2CEF-41A7-B5EF-4C3BDF21A034@gmail.com> (message from Yuan Fu on Sat, 24 Jul 2021 14:06:52 -0400) 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:271570 Archived-At: > From: Yuan Fu > Date: Sat, 24 Jul 2021 14:06:52 -0400 > Cc: Stefan Monnier , > cpitclaudel@gmail.com, > emacs-devel@gnu.org > > > We should ask the TS developers to provide a way of specifying custom > > memory allocation/release function as part of TS initialization. It > > is a feature many packages provide. > > I commented on tree-sitter’s 1.0 checklist. Thanks. > > Isn't there a better way of updating those than manually take them out > > of the TS grammar? Maybe write a short program linked against TS that > > would spill them in some format that's convenient to use? Manual > > updates are a serious maintenance burden. > > How does this convenient format looks like, in your mind? The grammar definition is already the “source”, I don’t see a way to magically make it easier to work with. What does “manual updates” refer to? If you mean updating patterns like > > (init_declarator > declarator: (identifier) @font-lock-variable-name-face) > > (parameter_declaration > declarator: (identifier) @font-lock-variable-name-face) > > when a language’s grammar changes, I don’t think we need to update them often, or ever. And It is not harder than updating font-lock-keywords when a language adds a new fancy syntax. It isn't an immediate problem, so we can delay it for later. However, I do worry about the ability to update this in some non-manual way. Take for example the way we update our character databases when Unicode adds more characters/scripts: we use the data files distributed by the Unicode Consortium and process them with scripts in admin/unidata to produce intermediate files in a format convenient for processing by Emacs, then we process those intermediate files as part of building Emacs. Unicode files change maybe or twice a year, but still, doing all those changes manually would be a burden.