develooper Front page | perl.perl6.internals | Postings from November 2002

Re: Draft sketch of bytecode generation

Thread Previous | Thread Next
From:
Dan Sugalski
Date:
November 6, 2002 12:47
Subject:
Re: Draft sketch of bytecode generation
Message ID:
a05200f09b9ef2f3546cf@[63.120.19.221]
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
dan@sidhe.org                         have teddy bears and even
                                       teddy bears get drunk

Thread Previous | Thread Next


nntp.perl.org: Perl Programming lists via nntp and http.
Comments to Ask Bjørn Hansen at ask@perl.org | Group listing | About