Stackless Python, eventual merge?

[Christian Tismer]

Greg Ewing wrote:
> Martin v. Loewis wrote:
> 
>>
>> They aren't really dangerous, just unconventional.
> 
> 
> 
> Last I heard, Christian was moving pieces of the C
> stack while there could be pointers to it in use.
> That's definitely dangerous, as he discovered when
> it broke Tk.

And I fixed it by adding some small locking code
to _tkinter that prevends stack slicing in that
context.

> I'd be very nervous about using Stackless until
> it stops doing that.
> 
>  > And that cannot be
>  > fixed, as it is essential to operation of Stackless.
> 
> Seems to me it could be fixed by just copying the
> C stack as a whole, instead of piecemeal.

See my other posting. Everything is there already.
Everything is under your control and optional.

hard-to-discuss-if-people-haven't-even-looked-at-it - chris

-- 
Christian Tismer             :^)   <mailto:tismer at tismer.com>
Mission Impossible 5oftware  :     Have a break! Take a ride on Python's
Johannes-Niemeyer-Weg 9a     :    *Starship* http://starship.python.net/
14109 Berlin                 :     PGP key -> http://wwwkeys.pgp.net/
work +49 30 89 09 53 34  home +49 30 802 86 56  pager +49 173 24 18 776
PGP 0x57F3BF04       9064 F4E1 D754 C2FF 1619  305B C09C 5A3B 57F3 BF04
      whom do you want to sponsor today?   http://www.stackless.com/