On Thu, Aug 11, 2011 at 1:07 PM, BGB <cr88...@gmail.com> wrote: > this would have a notable impact on the design of an HLL (and couldn't just > be retrofitted onto an existing traditional OO language such as ActionScript > or C#). >
That's a fair point. Some projects such as Joe-E [1] achieve something similar to a retrofit, requiring developers to write code in a safe subset of a language. JavaScript is also becoming more capability oriented, with the EC5 'strict' mode supporting a transition phase [2]. [1] http://en.wikipedia.org/wiki/Joe-E [2] http://wiki.ecmascript.org/doku.php?id=harmony:harmony > a model based on permissions/... potentially offers a bigger safety net, > since even if one can get a reference to something, they can't likely use > it. > Ah, but like most nets, you're likely to have a lot of holes. Managing permissions is even more painful than managing explicit static types and explicitly propagating error codes. It is not first on the mind of most developers. One of the big advantages of ocaps is that it tends to put security on the path of least resistance - i.e. developer laziness and security are coupled [2]. [2] http://www.youtube.com/watch?v=eL5o4PFuxTY > > yes, but it can also be noted that having to use 'cat' instead of 'cp', in > a general sense, would impact the system in very fundamental ways. > Security will impact a system in very fundamental ways. ;-) Regards, Dave
_______________________________________________ fonc mailing list fonc@vpri.org http://vpri.org/mailman/listinfo/fonc
