[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Dynamic loading progress
From: |
Stefan Monnier |
Subject: |
Re: Dynamic loading progress |
Date: |
Mon, 24 Aug 2015 15:11:33 -0400 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) |
> 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
- Re: Dynamic loading progress, Ted Zlatanov, 2015/08/19
- Re: Dynamic loading progress, Stephen Leake, 2015/08/20
- Re: Dynamic loading progress, Aurélien Aptel, 2015/08/23
- Re: Dynamic loading progress, Tom Tromey, 2015/08/24
- Re: Dynamic loading progress, Stefan Monnier, 2015/08/24
- Re: Dynamic loading progress, Paul Eggert, 2015/08/24
- Re: Dynamic loading progress, David Kastrup, 2015/08/25
- Re: Dynamic loading progress, Stefan Monnier, 2015/08/25
- Re: Dynamic loading progress, Paul Eggert, 2015/08/26
- Re: Dynamic loading progress, Aurélien Aptel, 2015/08/27