Thread-killing, round 666 (was Re: Lisp mentality vs. Python mentality)
vseloved at gmail.com
Tue Apr 28 04:47:10 CEST 2009
On Apr 27, 11:31 pm, David Bolen <db3l.... at gmail.com> wrote:
> I'm curious - do you know what happens if threading is implemented as
> a native OS thread and it's stuck in an I/O operation that is blocked?
> How does the Lisp interpreter/runtime gain control again in order to
> execute the specified function? I guess on many POSIX-ish
> environments, internally generating a SIGALRM to interrupt a system
> operation might work, but it would likely have portability problems.
We're arguing to the old argument, who knows better, what the
programmer wants: language implementor or the programmer himself.
AFAIK, Python community is on former side, while Lisp one -- on the
later. As always, there's no right answer.
More information about the Python-list