[e-lang] E research topics

[David Wagner]

Zooko writes:
> So my wish is that someone invent a way to securely re-use native  
> code libraries in E applications.

Kevin asks:
> What exactly do you mean by "securely"? How do you propose to  
> restrict it?

Zooko responds:
>I mean that the library that I'm re-using does not get authority that I didn't
>explicitly grant it, including authority to modify my persistent state
>(filesystem), connect to the network, read or write the non-granted state of my
>program (i.e. memory safety), etc..

Good luck, brother!  While this would be nice, I don't think you're likely
to get it, if you also require the abiliity to re-use most existing native
code and legacy libraries written in C, C++, etc.  Even if you put the
library in a separate process and use IPC, how would you restrict what
files the legacy library can open?  I think this is a near-impossible
problem statement.  You can't get there from here.