On 5/2/05, Phil Tomson <ptkwt / aracnet.com> wrote:
> So I keep track of whether or not ruby has been initialized.  Each of the
> functions in the library calls the initialize_ruby() function first
> thing.  initialize_ruby() only really initializes ruby the first time
> (in order to save some time - I don't want to have to startup ruby for
> every function call and then finalize ruby at the end of each function
> call).  Since I don't know what the last call to the function library
> might be, I don't call ruby_finalize() in any of the library functions.
> I used to do this, but eliminating the ruby_finalize() call seems to have
> no ill-effects.  What are the consequences of not calling ruby_finalize()?
> 
> Phil
> 
> 

Could you conceivably use atexit() to to finalize ruby?