From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Dynamic loading progress Date: Mon, 24 Aug 2015 15:11:33 -0400 Message-ID: References: <54E2355A.90@87.69.4.28> <83vbj1u020.fsf@gnu.org> <54E24CA4.9020601@dancol.org> <83h9uk7ddb.fsf@gnu.org> <54E382A5.5030408@dancol.org> <54F789B2.6030105@dancol.org> <87egnel6ac.fsf@lifelogs.com> <87vbgpk1po.fsf@lifelogs.com> <85mw20gmeo.fsf@stephe-leake.org> <878u97nyjn.fsf@lifelogs.com> <86d1yirnqw.fsf@stephe-leake.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1440443550 28932 80.91.229.3 (24 Aug 2015 19:12:30 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 24 Aug 2015 19:12:30 +0000 (UTC) Cc: Daniel Colascione , Stephen Leake , Emacs development discussions To: =?windows-1252?Q?Aur=E9lien?= Aptel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Aug 24 21:12:08 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 1ZTxA7-0002DP-Td for ged-emacs-devel@m.gmane.org; Mon, 24 Aug 2015 21:12:08 +0200 Original-Received: from localhost ([::1]:56184 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZTxA7-00065i-BV for ged-emacs-devel@m.gmane.org; Mon, 24 Aug 2015 15:12:07 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:42202) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZTxA3-00065Y-Se for emacs-devel@gnu.org; Mon, 24 Aug 2015 15:12:04 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZTx9y-0001VM-Sp for emacs-devel@gnu.org; Mon, 24 Aug 2015 15:12:03 -0400 Original-Received: from mercure.iro.umontreal.ca ([132.204.24.67]:33172) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZTx9y-0001VG-NX for emacs-devel@gnu.org; Mon, 24 Aug 2015 15:11:58 -0400 Original-Received: from hidalgo.iro.umontreal.ca (hidalgo.iro.umontreal.ca [132.204.27.50]) by mercure.iro.umontreal.ca (Postfix) with ESMTP id 98B339C1BE; Mon, 24 Aug 2015 15:11:57 -0400 (EDT) Original-Received: from lechon.iro.umontreal.ca (lechon.iro.umontreal.ca [132.204.27.242]) by hidalgo.iro.umontreal.ca (Postfix) with ESMTP id 6D8CC1E5B9B; Mon, 24 Aug 2015 15:11:33 -0400 (EDT) Original-Received: by lechon.iro.umontreal.ca (Postfix, from userid 20848) id 5666DB4288; Mon, 24 Aug 2015 15:11:33 -0400 (EDT) In-Reply-To: (=?windows-1252?Q?=22Aur=E9lien?= Aptel"'s message of "Mon, 24 Aug 2015 00:45:41 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-DIRO-MailScanner-Information: Please contact the ISP for more information X-DIRO-MailScanner: Found to be clean X-DIRO-MailScanner-SpamCheck: n'est pas un polluriel, SpamAssassin (score=-2.82, requis 5, autolearn=not spam, ALL_TRUSTED -2.82, MC_TSTLAST 0.00) X-DIRO-MailScanner-From: monnier@iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 132.204.24.67 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:189121 Archived-At: > Ok, we can always check for conservative scanning at compile to > enable modules. Exactly. >> We just need to export the equivalent of "staticpro" (ideally, this >> should keep track of which module called it, so that we can >> automatically "unpro"tect those vars when/if the module is unloaded). > So if I understand correctly, with conservative scanning there's no > need to call UNGCPRO? Indeed, neither GCPRO nor GCUNPRO. > Since module writer will often need to use Lisp_Object as handle for > their own struct pointers, I was thinking adding a way to register > finalizer functions to the API. We'll probably want ways to define new types and/or to register finalizers, indeed. But that can wait. Stefan