Re: compile-time taint checking and the halting problem

Oops, replied to the wrong message (that's why there was a "(COPY)" there). "David L. Nicol" wrote: > > Steve Fink wrote: > > > It's standard semantic analysis. Both your taintedness analysis and my > > reachability analyses can be fully described by specifying what things > > generate the char

Re: (COPY) compile-time taint checking and the halting problem

Steve Fink wrote: > It's standard semantic analysis. Both your taintedness analysis and my > reachability analyses can be fully described by specifying what things > generate the characteristic you're analyzing, what things block (in the > literature, "kill") it, and the transfer rules. It's ofte

Re: (COPY) compile-time taint checking and the halting problem

(moved off of -meta) "David L. Nicol" wrote: > > Steve Fink wrote (and I edited slightly): > > > I can't figure out why so many people misinterpret my RFC12 > > as requiring a solution to the halting problem. > > a large class of incompletely expressed > suggestions appear to get grouped int

stackless python

http://www.oreillynet.com/pub/a/python/2000/10/04/stackless-intro.html -- May the best description of competition prevail. (via, but not speaking for Deutsche Bank)