Re: Draft sketch of bytecode generation

[Dan Sugalski]

At 11:51 PM +0530 11/6/02, Gopal V wrote:

If memory serves me right, Dan Sugalski wrote:

  (Parrot bytecode is inherently  unverifiable as well, at least in
  the general case, which exacerbates the problem)

Hmm... Why ? ... Loose typing ?

Or does it just become an undecidability problem ?...

Loose typing is one reason, as is the potential for self-modification, by direct code rewriting, sub definition changes, and runtime code production. It's one of those halting problem issues--we can't tell whether the code is safe without running it.

That's why more effort's been put into thinking about runtime security issues, including resource limits and privilege assignment.
--
Dan

--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk