Re: Guile library behaviour

[Lynn Winebarger]

On Wednesday 17 April 2002 03:15, Daniel CAUNE wrote:
> I don't clearly understand the main idea of the Guile library
> initialization design. How can use it in an application that must be
> independent from a script interpreter (dynamic load and unload)?
> 
   Dynamic unload?  
   The garbage collector absolutely must know where the bottom of the
stack is to do its job.  You don't "initialize" guile and then do something,
you hand it your real main function and don't return until you're ready to
exit.  
    The only other way would be if someone modified guile to allow passing
in the bottom of the stack as initialization.  In the multi-threaded
case, it would have to know the bottoms of all the stacks, but I really don't
know what the status of guile's win32 thread support is, if any.  
     The other issue that would remain is that the garbage collector can't
be removed until it knows everything it's responsible for collecting has
been collected.  
      There might be other issues as well.

Lynn