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: Mon, 26 Jul 2021 15:56:12 +0300 Message-ID: <831r7lw7wz.fsf@gnu.org> References: <83h7gw6pyj.fsf@gnu.org> <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> <837dhew6r5.fsf@gnu.org> <861r7l7j9n.fsf@stephe-leake.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16094"; 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 Mon Jul 26 14:57:20 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 1m80Aa-000445-26 for ged-emacs-devel@m.gmane-mx.org; Mon, 26 Jul 2021 14:57:20 +0200 Original-Received: from localhost ([::1]:55746 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m80AZ-0000PI-0U for ged-emacs-devel@m.gmane-mx.org; Mon, 26 Jul 2021 08:57:19 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46562) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1m809f-0007uq-KK for emacs-devel@gnu.org; Mon, 26 Jul 2021 08:56:24 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:40362) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1m809d-0005Wm-Lw; Mon, 26 Jul 2021 08:56:21 -0400 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:4729 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 1m809c-0007Md-W1; Mon, 26 Jul 2021 08:56:21 -0400 In-Reply-To: <861r7l7j9n.fsf@stephe-leake.org> (message from Stephen Leake on Sun, 25 Jul 2021 22:10:12 -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:271644 Archived-At: > From: Stephen Leake > Cc: casouri@gmail.com, cpitclaudel@gmail.com, monnier@iro.umontreal.ca, > emacs-devel@gnu.org > Date: Sun, 25 Jul 2021 22:10:12 -0700 > > >> 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? > > The module interface layer of wisi.el would do: > > (signal 'error "parser ran out of memory") We don't have such an error (and handling an error when you've run out of memory could backfire). > >> 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? > > As other lisp symbols. Not sure, perhaps you could free them in a finalizer instead. If you want GC to free them, then yes.