John Tobey wrote: > Picture this. A Lisp (or Java, ...) structure holds a Perl > interpreter. A Perl variable holds a reference to the Lisp structure. > Structure and interpreter become inaccessible to all threads. Perl > will never know it's done with the Lisp structure, neither Perl nor > the structure will ever be collected, and we will have defeated > mark-and-sweep. FWIW, this isn't a case I'm worried about. If an embedding program doesn't explicitly destroy an interpreter, then its reasonable to assume that the interpreter's not dead and shouldn't be cleaned up after--if someone's leaking interpreters then, well, they've got bigger problems than the odd foreign object. :) Dan --------------------------------------"it's like this"------------------- Dan Sugalski even samurai [EMAIL PROTECTED] have teddy bears and even teddy bears get drunk
- Re: RFC: Foreign objects in perl Dan Sugalski
- Re: RFC: Foreign objects in perl John Tobey
- Re: RFC: Foreign objects in perl Dan Sugalski
- Re: RFC: Foreign objects in perl John Tobey
- Re: RFC: Foreign objects in perl John Tobey
- Re: RFC: Foreign objects in perl Ken Fox
- Re: RFC: Foreign objects in perl John Tobey
- Re: RFC: Foreign objects in perl Ken Fox
- Re: RFC: Foreign objects in perl John Tobey
- Re: RFC: Foreign objects in perl Brock
- Re: RFC: Foreign objects in perl Dan Sugalski
- Re: RFC: Foreign objects in perl John Tobey
- Re: RFC: Foreign objects in perl Ken Fox
- Re: RFC: Foreign objects in perl Dan Sugalski
- Re: RFC: Foreign objects in perl Ken Fox
- Re: RFC: Foreign objects in perl Dan Sugalski
- Re: RFC: Foreign objects in perl Dan Sugalski
- Re: RFC: Foreign objects in perl Ken Fox
- Re: RFC: Foreign objects in perl Dan Sugalski
- Re: RFC: Foreign objects in perl Ken Fox
- Re: RFC: Foreign objects in perl Dan Sugalski