Thread-killing, round 666 (was Re: Lisp mentality vs. Python mentality)
aahz at pythoncraft.com
Mon Apr 27 02:20:58 CEST 2009
In article <793a5176-ec2d-4ffd-b1e7-76207773350e at v35g2000pro.googlegroups.com>,
Vsevolod <vseloved at gmail.com> wrote:
>On Apr 26, 6:28 pm, a... at pythoncraft.com (Aahz) wrote:
>> The problem is that thread-killing (in the literal sense) doesn't work.
>> Unlike processes, there's no thread-environment encapsulation at the OS
>> level, which means that things don't get cleaned up properly. Even Java
>> has mostly given up on thread-killing. The only way to kill threads
>> safely is to have them terminate themselves. Your other option is to use
>> multiple processes.
>Well, somehow, in Lisp it's not a problem. :)
Does Lisp even have OS-level threads? What Lisp are you using, on what
OS? Are they perhaps Erlang-style cooperative threads instead?
Aahz (aahz at pythoncraft.com) <*> http://www.pythoncraft.com/
"If you think it's expensive to hire a professional to do the job, wait
until you hire an amateur." --Red Adair
More information about the Python-list