From: "Dan Sugalski" <[EMAIL PROTECTED]> Sent: Tuesday, December 02, 2003 5:27 PM
> Well, bah. I'll disable the table freeing for now and that should > take care of the bug at the moment, though it certainly won't cure > the underlying memory leak. > > Arguably, and this is getting into the realm of embedding, since this > is something that's set up by the global initialization, it should > stay in existence until the embedder calls the global destruction > code What about a counter of the vtable users(interpreters)? >, since it's possible (though I'm not sure we want to support it) > that after destroying all the extant interpreters that the embedding > program will want to create another one. As it has already been told, it's no problem -- you just call make_interpreter() and all the initialization is done for your new interpreter all over again including creating a vtable 0x4C56
