On 05.02.2013 18:01, William A. Rowe Jr. wrote:
What if both attempt to register an identical apr_optional_fn for
tcl_destroy. That way you will never have both optional functions
called.
My plan was for each of the modules to skip the destruction, if the OTHER module
is registered to run clean-up AFTER it.
This way the last module in the list will always run the destructor.
FWIW I would call that function as a destructor of the process_pool,
which you can find by walking the config pool's parents.
That's an idea... But, I think, I found a Tcl-specific solution for this
particular problem -- instead of calling Tcl_Finalize(), which ruins libtcl for
everyone in the same process, mod_rivet should simply delete the Tcl-interpreter
it created (websh does limit itself to exactly that already).
Let's see, what mod_rivet maintainers have to say
(https://issues.apache.org/bugzilla/attachment.cgi?id=29923&action=diff).
But this was a very educating thread nonetheless. Thank you, everyone. Yours,
-mi
