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: Sun, 25 Jul 2021 22:09:02 +0300 Message-ID: <837dhew6r5.fsf@gnu.org> References: <83h7gw6pyj.fsf@gnu.org> <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> <83eebo1c9z.fsf@gnu.org> <86wnpe6znx.fsf@stephe-leake.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32450"; mail-complaints-to="usenet@ciao.gmane.io" Cc: casouri@gmail.com, emacs-devel@gnu.org, cpitclaudel@gmail.com, monnier@iro.umontreal.ca To: Stephen Leake Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Jul 25 21:10:16 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 1m7jVw-0008GX-SR for ged-emacs-devel@m.gmane-mx.org; Sun, 25 Jul 2021 21:10:16 +0200 Original-Received: from localhost ([::1]:53838 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m7jVu-00061m-Ud for ged-emacs-devel@m.gmane-mx.org; Sun, 25 Jul 2021 15:10:14 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:43950) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m7jUv-0005KB-5P for emacs-devel@gnu.org; Sun, 25 Jul 2021 15:09:13 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:43296) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m7jUu-00045N-9j; Sun, 25 Jul 2021 15:09:12 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:3339 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 1m7jUt-0006We-PO; Sun, 25 Jul 2021 15:09:12 -0400 In-Reply-To: <86wnpe6znx.fsf@stephe-leake.org> (message from Stephen Leake on Sun, 25 Jul 2021 11:01:22 -0700) 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:271623 Archived-At: > From: Stephen Leake > Cc: Yuan Fu , cpitclaudel@gmail.com, > monnier@iro.umontreal.ca, emacs-devel@gnu.org > Date: Sun, 25 Jul 2021 11:01:22 -0700 > > >> How do we handle such thing in Emacs? > > > > We use xmalloc, which calls memory_full when allocation fails, which > > releases some spare memory we have for this purpose, and tells the > > user to save the session and exit. > > I'm thinking about how this applies to wisi, when migrating to a module. > > Ada has a built-in allocator; it's probably possible to change that, but > I'd like to understand exactly why we need to do that. We need that to allow the user to save the session while he/she can. > The Ada allocator throws an exception on allocation fail; is it > sufficient to turn that exception into an elisp signal, and arrange for > elisp to call memory_full (or take some other action, like killing the > parser)? What is a "lisp signal" in this context? > Another possible reason to change the Ada allocator is if we want to > expose Ada memory pointers directly to elisp, as Yuan Fu wants to do for > tree-sitter (I don't plan to do this for wisi). Does that require that > the pointers be allocated by the same allocator? Same allocator as what? > I'm not clear what that would mean for the garbage collector; is it > then expected to recover the tree-sitter-allocated memory for the > tree? or does it ignore those lisp objects? It depends on which Lisp object you wrap those pointers. User-pointer object allow you to provide your own "finalizer" function.