Greg Ewing wrote:
> Christian Tismer <tismer@tismer.com>:
>
>
>>Incredibly bad! Bad style, even worse, bad for me.
>
>
> I wouldn't call it "bad style" in general -- it's
> perfectly legal to pass the address of a local variable
> to another function, as long as the other function uses
> it before returning.
Maybe, but I'm really fucked up...
Saying "bad style" might help to keep people from
producing more problems :-)
Full stack analysis is really hard at this stage.
On the other hand, I think I have a work-around
that might work in most cases:
Right now, I install kinda "stack root", whenever
I see an initial frame, that is one with no f_back.
Maybe that's just bad. I saw myself moving 8kb of
stack away in the context of Tk. this is obviously
a large "installation" on the stack.
I might instead enforce the user to start a new
"root", manually. This would then no more start
automagically, but "by hand", on top of any stack
stuff that I better should not touch.
what would you suggest? -- ciao - chris
--
Christian Tismer :^) <mailto:tismer@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/
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4