> the interactions between that and encapsulation. If I can generate code at > runtime that gets compiled within a resolution contour that I myself don't > have access to, that's a potentially big problem. But the problem doesn't > lie in the fact that I generated code. It lies in the fact that the > mechanism allowed me to violate an encapsulation boundary.
hmm, security is a large topic. denial of resources like hogging the cpu can matter. yes the "system" should handle that better, but it probably doesn't. :-} so if i can sneakritly compile an infinite tight loop and execute it, that probably sucks. _______________________________________________ bitc-dev mailing list [email protected] http://www.coyotos.org/mailman/listinfo/bitc-dev
