[cap-talk] Worst-case object-capability language retrofitting
david.hopwood at industrial-designers.co.uk
Sun Sep 14 19:18:53 CDT 2008
Mark Miller wrote:
> Actually, I just remembered another that you mentioned earlier in this
> thread: legacy compatibility / retrofit effort. Each substrate will have its
> own unique legacy with its own unique problems. Having spent more than a
> year now on perhaps the worst case for an achievable language retrofit --
> has on other design decisions.
Actually, I think C might be achievable. If so, that would certainly be a
implemented as, a memory-unsafe language, there are already memory-safe
implementations of it (e.g. Fail-Safe C
<https://staff.aist.go.jp/y.oiwa/FailSafeC/index-en.html>), and it would
be interesting to try to make one of those capability-secure.
More information about the cap-talk