Re: Dynamic loading progress

[Stefan Monnier]

> 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