[Stackless] Re: [Python-Dev] Stackless pages
jeremy at alum.mit.edu
Mon Nov 6 20:33:14 CET 2000
>>>>> "CT" == Christian Tismer <tismer at tismer.com> writes:
>> I should clarify exactly what I am worried about with C API
>> calls. I don't care if they never return, which is already
>> possible since it could invoke some Python code that goes into an
>> infinite loop. I am worried about a C API call that itself never
>> returns even though one of its parents does.
CT> Shure. It does return, but it might not have done its expected
CT> work. Instead it tells you that some work needs to be done.
>> I am worried, as Christian explained, about a C API call that
>> receives the "unwind token" when it isn't expecting it.
CT> This can never happen. All those functions a new functions. All
CT> old functions do what they tell to do.
I'm getting closer, but still not there. Your first response says it
will return but it may not have done what was expected. Your second
response says this can never happen. I thought I was asking the same
question both times :-).
If we pick an old function -- PySequence_Tuple -- what happens when it
recursively invokes the interpreter mainloop at then calls a
continuation that was bound before the call to PySequence_Tuple?
Stackless mailing list
Stackless at starship.python.net
More information about the Stackless