Stackless Python, eventual merge?

[Greg Ewing]

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.

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.

-- 
Greg Ewing, Computer Science Dept,
University of Canterbury,	
Christchurch, New Zealand
http://www.cosc.canterbury.ac.nz/~greg